Repository navigation
docs(agents): sync from rivet-dev/agents - #129
Conversation
|
🚅 Deployed to the website-pr-129 environment in rivet-website
|
![the-company-company[bot]](https://avatars.githubusercontent.com/in/3874572?s=60&v=4){kind=small}
| @@ -1,189 +0,0 @@ | |||
| --- | |||
There was a problem hiding this comment.
🟠 Medium · Preserve the removed Pi Durable route
Deleting this page leaves both links in src/content/posts/2026-10-07-introducing-pi-durable-for-rivet/page.mdx pointing at a missing /agents/docs/pi-durable/ route. The repository's built SEO check fails twice on those links, and deployed historical links would 404. Keep route compatibility by redirecting this path to /agents/docs/pi/ (or retain a forwarding page) when consolidating the content.
| @@ -1,33 +1,23 @@ | |||
| import { createRegistry } from "@earendil-works/pi-durable"; | |||
There was a problem hiding this comment.
🟠 Medium · Install the new direct dependency in connector quickstarts
This new import is not included in the GitHub connector's standalone npm add command, so the copied server relies on an undeclared transitive dependency and can fail to resolve under package managers that do not hoist it. The same mismatch exists in the updated Slack, Linear, and Discord server snippets. Add @earendil-works/pi-durable to all four connector install commands, as the main quickstart already does.
| await fetch(`https://api.github.com/repos/${task.input.repo}/issues/${task.input.pr}/comments`, { | ||
| method: "POST", |
There was a problem hiding this comment.
🟠 Medium · Make the retried comment phase idempotent
The architecture documented in this change reruns the current task phase after a crash. If GitHub accepts this POST and the Actor stops before the terminal checkpoint is committed, comment runs again and creates a duplicate PR comment, contradicting the guidance that tasks are for work that must finish exactly once. Key the outbound operation by task.id and find/update an existing marked comment on retry, or use an API operation with an idempotency key before committing completion.
![rivet-docs-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
4d886cd to
04b814e
Compare
| @@ -1,189 +0,0 @@ | |||
| --- | |||
There was a problem hiding this comment.
🟠 Medium · Preserve the removed Pi Durable route
Deleting this page leaves both links in src/content/posts/2026-10-07-introducing-pi-durable-for-rivet/page.mdx pointing at a missing /agents/docs/pi-durable/ route. The repository's built SEO check fails twice on those links, and deployed historical links would 404. Keep route compatibility by redirecting this path to /agents/docs/pi/ (or retain a forwarding page) when consolidating the content.
| @@ -1,33 +1,23 @@ | |||
| import { createRegistry } from "@earendil-works/pi-durable"; | |||
There was a problem hiding this comment.
🟠 Medium · Install the new direct dependency in connector quickstarts
This new import is not included in the GitHub connector's standalone npm add command, so the copied server relies on an undeclared transitive dependency and can fail to resolve under package managers that do not hoist it. The same mismatch exists in the updated Slack, Linear, and Discord server snippets. Add @earendil-works/pi-durable to all four connector install commands, as the main quickstart already does.
| await fetch(`https://api.github.com/repos/${task.input.repo}/issues/${task.input.pr}/comments`, { | ||
| method: "POST", |
There was a problem hiding this comment.
🟠 Medium · Make the retried comment phase idempotent
The architecture documented in this change reruns the current task phase after a crash. If GitHub accepts this POST and the Actor stops before the terminal checkpoint is committed, comment runs again and creates a duplicate PR comment, contradicting the guidance that tasks are for work that must finish exactly once. Key the outbound operation by task.id and find/update an existing marked comment on retry, or use an API operation with an idempotency key before committing completion.
This branch was successfully deployed
2 participants
Automated docs sync from
rivet-dev/agents@d08130d.Do not edit
vendor/agents/here. Edit the docs inrivet-dev/agentsand this PR updates itself.