agents client: remove dependency on agentd HTTP API

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

Dependencies

Description

Edit

Remove HTTP daemon client usage from Omni/Agents/Client.hs.

Context: Omni/Agents/Client.hs currently targets the agentd HTTP API. With daemon removal, this should be replaced.

Scope:

  • Replace HTTP calls with direct CLI integration (invoking agentd subcommands) or direct library calls.
  • Remove AGENTD_URL dependency for agent lifecycle operations.
  • Keep returned data model stable enough for callers (or update callers in same change).

Acceptance:

  • No runtime dependency on agentd HTTP API endpoints.
  • Agent lifecycle operations still work from callers that currently use Omni/Agents/Client.hs.

Git Commits

00b3042efeat(agents): replace agentd HTTP calls with local runtime APIs
Coder Agent3 days ago3 files

Timeline (4)

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

Replaced Omni.Agents.Client HTTP code with direct Omni.Agentd.Daemon runtime calls (list/get/create/start/send/stop/remove, message fetch). Removed AGENTD_URL usage and updated Ava call sites to use the new client path. Verified with bild --test Omni/Agentd.hs, bild Omni/Ava/Web.hs, and bild Omni/Ava/Telegram/Developer.hs. Commit: 00b3042e

🔄[human]InProgress → Review3 days ago