It is not just remote control
`asynq-agentd` sits below the UI layer. It is a local runtime that manages sessions, tasks, approvals, recent work, terminal streams, and restart recovery.
Open-source local-first agent runtime
asynq-agentd is an open-source daemon and operator CLI for Claude Code, Codex, and future coding agents. It handles task orchestration, approvals, recent-work continuity, recovery, and live operator surfaces on top of the machine you already trust.
`asynq-agentd` sits below the UI layer. It is a local runtime that manages sessions, tasks, approvals, recent work, terminal streams, and restart recovery.
The daemon already exposes dashboard-oriented endpoints for overview, attention-required, and continue-working cards. That same contract is intended to power Asynq Buddy.
The runtime stays open and local-first. The future Buddy product is the polished operator experience on top: better UX, mobile workflows, pairing, and presence-aware notifications.
What it already does
Best fit today
Developers who want a trustworthy local daemon for coding agents, plus teams that want an open backend contract they can wire into their own dashboards before a full hosted product exists.
curl -fsSL https://agentd.asynq.org/install.sh | sh
irm https://agentd.asynq.org/install.ps1 | iex
Today the hosted entrypoints are thin wrappers: they clone the repo into a temporary directory and run the real bootstrap installer from source. Tailscale-aware onboarding is included in the installer flow.
Read the contract
The daemon already exposes enough contract surface to build dashboards, operator tooling, or your own UI on top of it.
Read API contractUse it today
`asynq-agentctl` can already inspect agents, sessions, approvals, recent work, pairing, dashboard cards, and auth tokens without dropping to raw curl for common tasks.
Read usage examplesOpen-source scope
asynq-agentd is the daemon, runtime contract, and local operator layer. Asynq Buddy is the future product experience built on top of it. That split keeps the runtime open, inspectable, and useful on its own while the higher-level UI evolves separately.