richardcase / richardcase/clowder
Scheduled or queued agent spawning
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 16
Description
SpawnAgent is purely on-demand today — there's no scheduling or queueing primitive anywhere in the daemon or protocol.
Proposal: support two related but distinct capabilities — (a) cron-like scheduled spawns ("spawn this agent profile daily at 9am") and (b) a work queue ("queue N tasks against a profile, run at most M concurrently"). Worth scoping as to whether this lives in the daemon or as a client-side convenience that repeatedly calls SpawnAgent.
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 by tracing the existing SpawnAgent entry point through the daemon and protocol. Compare daemon-side scheduling and queueing with a client-side implementation that repeatedly calls SpawnAgent, then define the scope and concurrency behavior for cron-like spawns and bounded work queues. Done means the project has an agreed design for both capabilities and their ownership.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100