Repository navigation
Build portable agent-home v0.1.0 - #2
Conversation
|
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9afb0aca21
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| await this.gateway.comment(number, event("claim", "verified", "Task moved to agent:active.", this.actor)); | ||
| return this.gateway.update(number, { labels: nextLabels(issue, "agent:active") }); |
There was a problem hiding this comment.
If the subsequent GitHub update fails because of a transient API error, rate limit, or permission problem, this comment permanently records a verified move to agent:active while the issue retains its previous state; the same ordering affects block and completion. Avoid publishing a successful audit result until the update succeeds, and handle the remaining comment-failure case explicitly so the canonical history cannot contradict the labels.
AGENTS.md reference: AGENTS.md:L9-L9
Useful? React with 👍 / 👎.
| labels: ['agent:inbox'], | ||
| }); |
There was a problem hiding this comment.
Each successful scheduled run now creates a labeled agent task, but the workflow only emits a runner notice and never comments on the new issue. Consequently this task mutation has no durable action/result/evidence event in the canonical ledger; add the same concise creation audit comment used by TaskService.createTask.
AGENTS.md reference: AGENTS.md:L9-L9
Useful? React with 👍 / 👎.
1 participant
Outcome
Turns the repository into an Apache-2.0 agent-home template with GitHub Issues as the canonical ledger, one portable Skill, Codex/Claude/ZCode packaging, and an optional user-owned Vercel MCP.
Safety boundary
Verification
npm run checkDeliberately external smoke
The four-client same-private-fork smoke requires a user-owned Auth0/Vercel deployment and client accounts. The hosted smoke workflow and release checklist are included; it is not falsely marked complete from unit tests.