-
Notifications
You must be signed in to change notification settings - Fork 0
epic: agentd v0.1.0 implementation #24
Copy link
Copy link
Open
Description
Summary
Implement agentd to the point where an operator can configure agents, start the daemon, trigger a session, and watch an agent do runa-managed work through a methodology plugin inside a Podman container. Manual session triggers only — scheduling comes later via agentd-scheduler.
Done Condition
agentd starts as a daemon, reconciles stale resources from prior runs, and accepts session triggers. A triggered session creates an ephemeral Podman container where the agent has identity, credentials, methodology, and runa manages the groundwork topology on a real project. The container is destroyed when the session completes.
Task Issues
- chore: remove mcp-transport and forgejo-mcp crates #23 — Remove mcp-transport and forgejo-mcp crates
- feat(config): agent configuration format and parsing #25 — Config format and parsing
- feat(runner): session lifecycle — container creation through teardown #26 — Session lifecycle — container creation through teardown
- feat(daemon): daemon composition, credential resolution, and operator interface #28 — Daemon composition, credential resolution, and operator interface
Dependency Graph
graph TD
A[#23 crate cleanup] --> B[#25 config format]
B --> C[#26 session lifecycle]
C --> D[#28 daemon composition]
Layer 0 (no deps): #23 — crate cleanup ✅
Layer 1 (needs 0): #25 — config format and parsing ✅
Layer 2 (needs 1): #26 — session lifecycle
Layer 3 (needs 2): #28 — daemon composition, credential resolution, operator interface
Quality Standard
MVA — Most Viable Awesome. The smallest thing that is genuinely good.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels