Add agent webhook management - #648
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
2027 — Eval complete for commit
|
| URL | Mapping |
|---|---|
| digger.dev | → opensandbox-feat-agent-webhooks.mintlify.site |
| opencomputer.dev | → opensandbox-feat-agent-webhooks.mintlify.site |
2027 // complete the getting started guide at https://opencomputer.d — Did not finish
- ⚠️ Score nulled: AI judge determined the task was not completed — Agent installed the SDK and wrote the quickstart script exactly as documented, but could not obtain an API key: the CLI login triggers a device-code OAuth flow that redirects to a mandatory GitHub sign-in page in a browser, which the agent cannot complete. The quickstart script fails with a 401 and the task was left unfinished pending human credentials.Prompt
complete the getting started guide at https://opencomputer.dev
Commit b252d7d · View report →
Evaluating agent experience using 2027.dev · View dashboard
breardon2011
added a commit
that referenced
this pull request
Aug 20, 2026
main had rolled this work back in f25be77 ("bring back 608 basically since we haven't tested bleeding edge and reconfiguring") and then landed new work on top (#648 agent webhook management), so the conflicts are rollback-vs-reinstate rather than two parties editing the same lines. Resolved in favour of this branch, which is the tested reinstatement: - pool_stock.ts, wrangler.toml: main's only change since the merge base was the rollback's deletions (0 net additions), so this branch's versions are taken whole. A line-level merge here produced a mixture of the old claim() and the new claim-batch()/mintSandboxTokenDO() that did not typecheck. - index.ts: resolved per-hunk instead, NOT --ours, because main's #648 webhook routes live in this file and auto-merged cleanly outside the conflict regions. Both survive: webhook handling and the g3 shard re-placement plus the doin/up/ready instrumentation. Verified: tsc clean, 101 vitest tests pass, GOOS=linux go build ./cmd/... clean, go test ./internal/api/... ./internal/awsvm/... pass. internal/firecracker and a darwin-host cmd/agent build already fail on origin/main and are unrelated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Adds the public webhook invocation proxy, API/CLI lifecycle operations, agent-level Webhooks dashboard and sidebar entry, authoring types, and public documentation.
User flow
Users create an environment-scoped webhook in the dashboard or with
opencomputer webhooks create, save the one-time token, then POST{ text?, payload? }. The response links the fresh durable session. List output never returns the token.Verification
0.5.6; agent authoring types advance to0.5.2opencomputer-edge-mo-devversion528b694a-fe45-4cf9-aef1-48d50997d4a0mo-oc-devMerge order
Depends on the companion Blue backend PR. Publish the package versions after merge before documenting the CLI as generally available.