AmbitGet startedFAQReferenceGlossaryAll docsGitHubLive demo

The ideas behind Ambit

The claim

What an agent setup can do is composed from pieces configured separately. A configured piece may fail, and technical reach differs from permission. Ambit models those distinctions for a person, their agents and their machines.

Four names you will meet

They nest: the ambit is the reach, the frontier is its edge, the capability graph computes both, and the affordance frontier is the wider theory.

Name Where you meet it Meaning
Ambit README and app What you, your agents and machines can jointly do
Frontier Map, CLI and history The edge of that reach, with next steps beyond it
Capability graph Reference The nodes and dependencies used to compute reach
Affordance frontier Theory The broader object, including physical, social, institutional and economic action

The glossary defines the product's terms.

Three aims, one project

What is new

  1. Composition is computed. A vector store and local embeddings may satisfy the authored prerequisites of semantic retrieval, even though neither config names it. The frontier ledger distinguishes direct acquisitions from combinations reached through other changes. Built: ambit history since.

  2. Checks change availability. Structure (state) and verification health (lifecycle) are separate. A failing check excludes a capability from plans, permission decisions, rankings and simulations until it passes again. A node without a check remains unverified. Built: ambit verify.

  3. Automatic authority changes are asymmetric. Promotion needs a threshold set by a person; demotion follows one failing check. A forbidden grant wins at any specificity. Built: ambit can and ambit authority promote.

  4. Repeated blocks guide investigation. ambit next ranks recorded blocks, then structural leverage. An agent can draft an acquisition proposal, a person approves it, and the executor checks the signed approval before applying. ambit roi compares recorded intervention time afterward; it does not prove causation or financial returns.

  5. Reach has a history. Snapshots preserve states, kinds and lifecycles. The map replays gains and losses, using today's names and edges. Built: ambit history and the map's History.

Where it comes from

Attack graphs show how topology and permissions compose into reachable paths. The capability approach distinguishes resources from effective opportunities. Ambit uses that framing for productive action, combining dependency analysis with recorded checks and authority.

Configuration databases, workflow systems, agent evaluations and MCP gateways address related parts. The theory page gives the genealogy.

The next product question

Can this setup achieve this outcome, on this target, under these conditions?

The proposed next layer binds success criteria to the setup and evidence from each attempt. A complete release rehearsal would exercise delivery and recovery together. An owned paid service would also need customer acceptance, cash-flow and control records.

Work runs and outcome records exist. Versioned scenarios with acceptance evidence are proposed in roadmap §17, and unbuilt.

What it does not claim

To see these on a sample setup, open the demo. Why Ambit gives the argument, the affordance frontier the theory, and the reference the software.

See what your own agents can reach

Ambit reads the MCP configs of Claude Code, Cursor, OpenCode and thirteen more agents into one local map: every server, which ones work, what one more step would open, and what breaks if a piece goes.

Open the live demoa sample setup in your browser, nothing to install

On your machine: npx ambit-cli, with Node 22.18 or newer on macOS or Linux.

MIT licensed · one local SQLite file, no telemetry · on npm and in the official MCP registry