0xrsydn/research
1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
research/durable-agent-runtime/next-steps.md
hermes c978db1437 Restructure agent research under agent-infra umbrella 
- Add agent-infra umbrella topic (hub for state, harness, model-access, collaboration lenses)
- Split harness-engineering out of durable-agent-runtime; fold in Cloudflare Code Mode finding
- Narrow durable-agent-runtime to state/durability lens; retitle
- Tag codex-app-server-byo-auth as agent-infra subtopic
- Document umbrella-topic convention in README
2026-08-11 08:16:18 +00:00

1.2 KiB
Raw Blame History

Next Steps — Durable Agent Runtime

Part of durable-agent-runtime/index

Open questions

  • Which repos get the .agents/setup-style contract first (clan-private, law retrieval, idx-cli)?
  • Should the dev-server + ports-file pattern be a shared script library in clan-private or per-repo?
  • Is hypeman worth an evaluation build on hermes-vm (per-task VM with standby) vs NixOS containers?
  • Does the Forgejo webhook → kanban wake need a new service, or does an existing cron/webhook path cover it?
  • Code Mode pattern for our Effect TS stack now tracked in harness-engineering/index

Decisions made (2026-08-07)

  • Research topic: durable-agent-runtime — covers durable objects, stateful machines, and harness engineering (sandboxed or not). On 2026-08-11 harness engineering was split out into its own topic under the agent-infra umbrella.
  • Do NOT build a distributed durable-object layer (celld) or actor platform (rivet) on a single box.
  • Do NOT build an E2B-style per-thread VM fleet; use NixOS-native isolation when needed.
  • DO build environment contracts: per-repo setup hooks, AGENTS.md per repo, dev-server skills, event wake.