Skip to content
Browse the docs

What is Nested

Nested runs specialized coding agents on Kubernetes you control. Learn what it is, who it is for, and how the app, console, and runtime fit together.

Updated 3 min readView as MarkdownOpen in Nested

Nested in one paragraph#

Nested runs specialized coding agents inside a Kubernetes cluster that you operate. Each agent is a deployment with its own machine, tools, and sign-ins. You hand it work as a task, it works while you do something else, and it tells you when it needs you. Many tasks can run at the same time, across many agents.

Nested is not a multi-tenant SaaS. The control plane, the agent hosts, and the platform services (Postgres, Temporal, an S3-compatible object store, and more) install into your cluster, so prompts, repository context, and connector tokens stay inside a boundary you already secure.

Who it is for#

  • Engineers who want to hand off real work — a bug fix, a review, a migration, a report — and come back to a finished result instead of babysitting a chat window.
  • Platform teams who need agents to run next to their own workloads, under their own network policy, with their own credentials.
  • Security and compliance owners who need to know exactly where agent data lives. In Nested, the answer is: in the cluster you host.

The three surfaces#

SurfaceWho uses itWhat it does
The appEveryone on a teamChat-first workspace: start tasks, answer agents, run automations, read reports
The consoleOperatorsRegister clusters, manage the agent catalog and packs, operate deployments
The runtimeYour clusterEvery agent runs as a cloud-agent deployment next to the control plane and platform services

Most of these docs cover the app, because that is where people spend their day. The Platform section explains what runs underneath.

How work flows#

  1. You deploy an agent with New agent. A pack gives it skills, subagents, formulas, and MCP servers; secrets give it credentials.
  2. You start a New task, pick the agent and a workspace in the composer, and describe the work.
  3. The agent works on its own machine. If it needs an answer, a sign-in, or a decision, the task moves to Needs you at the top of your task list.
  4. You answer, or you mark the task done. Closed tasks move to Archived.
  5. For recurring or event-driven work, an automation starts tasks for you — on a schedule, from a webhook, from GitHub, from Slack, and more.

What makes Nested different#

  • Specialized agents, not one chatbot. Each agent carries the packs and secrets for its job, so its context stays focused.
  • Parallel, durable tasks. Tasks are not browser tabs. They keep running when you close the app, and you can reopen a closed one later.
  • Memory that belongs to you. What agents learn about you and your work lives in your memories, shared across every agent you use.
  • Your boundary. Data stays in the datastores that run in your cluster (Environments, if enabled, are the exception noted above). See the privacy policy.

How to read these docs#

Questions

Is Nested a hosted SaaS?
No. Nested installs into a Kubernetes cluster you operate. The control plane, agents, and datastores run there, and the vendor does not receive a copy of your content by default. Optional Environments run on a cloud provider.
Which coding agents can a Nested agent run?
The deploy wizard offers Cursor (the default), Claude Code, and Kimi CLI as presets. You can pick another agent with Choose from registry (the ACP registry) or Manual entry.
Do I need to know Kubernetes to use Nested?
No. People use the app to deploy agents and start tasks. Operators handle the cluster and the agent catalog in the console.