richardcase / richardcase/clowder
Fail agent spawn when registry persistence fails
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 16
Description
Problem
Agent spawn reports success after calling Registry::upsert, but persistence errors are logged and discarded. A read-only or full state filesystem creates a live agent that disappears after restart.
Evidence: https://github.com/richardcase/clowder/blob/b5492d5/crates/clowder-daemon/src/server.rs#L690-L706
Persistence path: https://github.com/richardcase/clowder/blob/b5492d5/crates/clowder-daemon/src/registry.rs#L52-L64
Acceptance criteria
- Propagate registry write errors to the spawn request.
- Roll back the newly-created pane/worktree when registration fails.
- Add a failure-injection test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in crates/clowder-daemon/src/server.rs around lines 690-706 and trace the Registry::upsert call, then read the persistence path in crates/clowder-daemon/src/registry.rs around lines 52-64. Make the spawn request report registry write failures, roll back the newly created pane/worktree, and add a failure-injection test covering the error path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100