KyberAgent is a workspace for running and coordinating a team of AI agents. One headless daemon owns the entire runtime — brains, sessions, the message bus, and orchestration — and every window, local or remote, is a lens onto it.
KyberAgent is a deployable kernel daemon that owns the entire runtime for a fleet of local and remote AI agents — their brains, sessions, message bus, orchestration, plugins, and skills. The desktop app attaches to it as one host among many.
The daemon is headless by design. It runs as its own process, so it survives app reloads and can run as a remote service that other machines attach to. Desktop and remote clients are clients, never owners — the daemon is the single source of truth.
An Orchestrator sits in front of the fleet — routing each request to the right specialist, delegating work, and synthesizing across agents into a single answer.
The one agent that ships built in. It reads intent, routes to the right specialist, and — when a question spans several agents — queries their brains and returns one unified answer. An inline trace shows exactly how it routed: Orchestrator → Arcana → reply.
A message bus carries query, notify, delegate, and response between agents — with broadcast, reply correlation, and loop detection built in.
Type @Athena to route a query to that agent and inline its reply — the chat box is a typed shell over the whole fleet.
One command turns a chat message into tracked work. Dispatch moves each issue through a phase machine on worker heartbeats, then lands the result in your inbox — diffs, summaries, and all.
A remote agent runs on its own daemon — a VPS or an always-on host — and you reach it over your private network, brain and all. Not a remote API call: a real agent, somewhere else.
A VPS-hosted agent provisions its own Dockerized GitHub environment, clones the repo, isolates on a work branch, and proxies its brain back to you — all on its own daemon.
Reached over a private tailnet — no public exposure.
A control plane is the single source of truth for who exists, who owns what, and what each user can do — and it never sees a brain, a connection token, or a single model call.
Orgs, users, teams, roles, agent ownership, access grants, and adapter allowlists. Never a brain, a token, or model traffic.
Brains, connection tokens, model traffic, and sessions live on your hosts — and that's where policy is enforced. Verification is offline: no call home on the request path.
Federate to Okta, Entra, Google, or Auth0. Daemons verify signed tokens offline against cached keys — enforcement never waits on a network round-trip.
Roles from Owner to Member, plus per-agent ownership. Grant agents at use or manage level, to a user or a team. Per-agent tiers: public, org, restricted, private.
Suspend a user and their access falls away within one short-lived policy window. Fail-closed by design: daemons keep enforcing last-known policy even offline — they never revert to open.
Allowlist providers and models across the org — a session requesting a disallowed provider is rejected. Do the same for connectors and MCP servers.
OAuth tokens live in the OS keychain, never in plaintext. Run the whole control plane in Docker against your own Postgres, behind your own domain — hosted or self-hosted is a config flip, and with SSO federation no user record leaves your infrastructure.
Each agent carries a persistent brain — timeline, entities, relationships, facts, and vector recall — that it maintains itself, local-first, with an optional cloud workspace.
Per-agent long-term memory in local SQLite: a timeline of events, an entity graph, facts with source confidence, and semantic recall. A background sleep pass consolidates the timeline into facts, entities, and routing heuristics — with an audit trail of every merge.
Swap any agent's brain from local to a shared cloud workspace and back — instantly, without losing a thing. Bring it home anytime.
Chat is just the front door. Each agent brings a working directory, a terminal, and git; the daemon projects shared surfaces alongside them.
KyberAgent ships with the Orchestrator. You assemble the rest — a docs & memory agent, a frontend agent, a remote sales agent, whatever your work needs — or add ones your team already deployed.
Local-first and solo on day one; org, team, and remote capabilities light up the moment you sign in. Nothing to rip out as you scale.
KyberAgent is in active development with enterprise design partners. Book a demo to see orchestration, remote and shared agents, and the control plane running on real hardware.