Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature request: webhook push mode for event delivery (in addition to SSE/polling)

未关闭
#94 2 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
bun, rust, typescript
领域
api, backend

调研方向

No file, test, or entry point is named. Start by locating the runtime's existing SSE and polling event-delivery paths and the normalized event representation; then determine how configuration, signing, retries, and deduplication fit together. Done means an optional webhook mode can deliver normalized events with the requested reliability and sequencing behavior.

由索引模型根据 Issue 内容生成。

描述

👋 Hey Team

I really liked the look of Agent Sandbox and wanted to use it as our primary orchestration engine instead of maintaining our own homegrown Bun executable.

My blocker is architectural: our app is async-first, and is designed to spin up a lot of sandboxes. For me it makes more sense for the sandboxes to update the api instead of long polling.

Today we persist sandbox/agent events by pushing them from sandbox -> API via webhooks.

Right now, SSE/long-polling is less ideal for our model and makes cutting over hard.

What would unblock us is an optional webhook push mode in the runtime. Add a configurable outbound webhook sink for normalized events, e.g.:

  • webhook URL
  • webhook secret/signing
  • retries with backoff
  • stable event id / sequence for dedupe

Happy to contribute a PR (but I believe this would be in rust and i have limited experience there)

主要语言
TypeScript
星标
1.6k
派生
134
平均合并
12 小时 54 分钟
30 天内合并 PR
41

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rivet-dev/agents 的其他 Issue

查看 rivet-dev/agents 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。