agentd: remove HTTP daemon and use CLI-only control plane

t-801·WorkTask·
·
·
Created3 days ago·Updated3 days ago·pipeline runs →

Dependencies

Description

Edit

Remove the agentd HTTP daemon surface and rely on CLI-only execution paths.

Scope:

  • Remove agentd daemon command and related CLI parser entries/help text.
  • Delete Omni/Agentd/Daemon.hs HTTP server/API handlers (runDaemon, Servant/Warp plumbing).
  • Preserve persistent session management features currently used by CLI by moving needed logic into CLI-owned modules (e.g. persistent/systemd/db helpers), not an HTTP service.
  • Remove daemon deployment path (Omni/Ide/deploy-agentd.sh) that starts agentd daemon ....
  • Update docs/specs to reflect CLI-only model.

Acceptance:

  • No agentd daemon command remains.
  • No HTTP daemon runtime path remains in agentd code.
  • Existing CLI workflows still work: create/start/status/send/logs/watch/top/stop/rm/purge.

Git Commits

c1a32928feat(agentd): remove daemon command and deployment path
Coder Agent3 days ago3 files

Timeline (6)

🔄[human]Open → InProgress3 days ago
💬[human]3 days ago

Removed the agentd daemon CLI command wiring, disabled runDaemon with explicit failure text, and replaced deploy-agentd.sh with a CLI-only no-op message. Added reusable getPersistentMessages helper for non-HTTP callers. Verified with bild --test Omni/Agentd.hs and bild --test Omni/Agentd/Daemon.hs. Commit: c1a32928. Note: Servant handler code remains in Omni.Agentd.Daemon but is now unreachable from CLI entrypoints.

💬[human]3 days ago

Opened follow-up t-806 (discovered-from t-801) to remove now-unreachable Servant daemon code and shrink Omni/Agentd/Daemon.hs. This patchset focuses on control-plane cutover: no daemon command/deploy path and no HTTP usage in runtime callers.

🔄[human]InProgress → Review3 days ago