Agentic

An agent that works like you do.

Giving your work a voice.

The building blocks answer problems that keep coming back. Coding agents ignore those answers and write their own.

In a project that already had a sign-in system, an agent built a second one beside it. Agents rewrite small tools the project already has, and the same correction has to be given again and again. If agents used the template as written, Foundry wouldn't need to exist.

Every new conversation with an agent starts half-amnesiac, so you explain how you work, what you decided and what you like all over again. These tools carry what you've already decided into every conversation, and let you decide who and what can reach your work.

Technical details

Oracle

Your agents stop making the same mistake.

Oracle figures out how to make your agent better on your project, from your own past work, and checks that it worked.

It tests each change to your docs and Wardens on work you already merged, with what you merged as the answer key, and keeps only the changes that hold.

Closed sourceWaitlist
Foundry

The workspace where it reaches your agent.

Foundry runs on your computer around Claude Code and Codex, on the subscriptions you already pay for, or inside agent apps such as Paseo and T3 Code.

Small agents called Wardens each hold one part of what your project knows, and remind your agent of it when your request touches that part. When Oracle changes a doc or a Warden, Foundry carries the change into your next session.

Free to use todaySource-available · BSL 1.1
Kingdom

Your accounts, and who may use them.

Kingdom holds the accounts you connect, such as GitHub, Slack and Linear, and your AI logins, across every team you're in.

It hands out Signets: passes with exactly the operations you choose, revocable at once. Teammates, their agents and your other machines work in your accounts without holding a key.

Hosted · closed sourceSome parts in progress
How it works

Your machine does the work, and Kingdom holds the credentials.

Your agent runs inside Foundry on your computer, on your own subscriptions. Steps 1 to 3 follow one request; 4 and 5 are how it learns. Anything that crosses to a teammate or a provider goes through Kingdom, on a Signet the owner can take back.

Colour: part
  • Agentic
  • Yours: your agent, code, accounts and people
  • Signet
  • Closed source
  • Building block (template)
Fill: status
  • Done
  • Under construction
  • Planned
Lines: relation
  • Works with
  • Goes through a Signet
  • Under construction
  • To a planned piece
How Foundry works, and where Kingdom fitsOn your machine, your agent (Claude Code or Codex) runs inside Foundry on your own subscription. 1: you ask your agent. 2: Wardens, small expert agents built from your docs (under construction: they come built in repos made from template, and building them for any repo is in progress), notice what the request touches. 3: they remind your agent of what your project already has, and where it's written down; your agent decides what to use. Then the loop that learns: 4: Archive keeps every session. 5: Oracle (closed source) checks whether a correction stuck, and proposes changes to the docs and Wardens. A codebase built from template comes with its Wardens built. Hosted: Kingdom (closed source, under construction) holds your accounts, such as GitHub, Slack and Linear, and anything that uses them goes through a Signet, a pass the owner can take back: Foundry pairs with Kingdom on one, teammates and their agents come in on one, and your command-line tools will run through Kingdom so no token sits on your machine, with KCP, the Kingdom CLI Proxy (signing in works; running commands is in progress). Artifactory, for sharing what agents make, is planned.HostedKingdom holds the keysOn your machineYour agent, on your own subscriptionFoundry sends every session to ArchiveFoundry pairs with Kingdom; the pairing is a SignetKCP will run your provider CLIs through Kingdom (in progress: it signs in today)teammates and their agents use your integrations through a Signetyour integrations connect to Kingdom, which holds their credentialsArtifactory will sign in with Kingdom (planned)integrationsGitHub, Slack, LinearsignetA pass you can take backkingdomYour accounts, and who may use themartifactoryShare what agents maketeammatesThem and their agents3your codebaseWhat Wardens remind your agent offoundryThe workspace around your agenttemplateComes with its Wardens builtkcpYour command-line tools, via Kingdom4archiveKeeps every sessionWardens notice what a request touches and remind your agent of what your project already has, and where it's written down; your agent decides what to useWardens are built from your codebase's docs, one per topica codebase built from template comes with its Wardens built and turned onOracle reads the sessions Archive keepsOracle checks whether a correction stuck and proposes changes to the docs and Wardens2wardensNotice what your request touches1your agentYou ask. Your agent decides.Learning from correctionsClosed source5oracleChecks fixes stick, proposes changes

Steps 1 to 3 follow one request; 4 and 5 are how it learns. Hover or focus a piece to light what it works with.

On your machineYour agent runs inside Foundry, on your own subscription
  • foundryThe workspace around your agent
  • 1your agentYou ask. Your agent decides.
  • 2wardensNotice what your request touches
  • 3your codebaseWhat Wardens remind your agent of
  • templateComes with its Wardens built
  • 4archiveKeeps every session
  • kcpYour command-line tools, via Kingdom
Learning from corrections
  • 5oracleChecks fixes stick, proposes changes
HostedAnything that uses your accounts goes through a Signet
  • kingdomYour accounts, and who may use them
  • signetA pass you can take back
  • integrationsGitHub, Slack, Linear
  • teammatesThem and their agents
  • artifactoryShare what agents make
Read the map as text

How to read the map: colour shows which part a piece belongs to (lime for Foundry and the agentic tools, blue for what is yours: your agent, your codebase, your accounts and the people you work with, pink for the Signet, charcoal for closed source, amber for template, a building block). Fill shows status: a solid block is done, a block in scaffolding is under construction, a dashed outline is planned. Lines show the relation: a lime line works with, a pink line goes through a Signet, a scaffold-dashed line is under construction, a long-dashed grey line reaches a planned piece. Steps 1 to 3 follow one request; 4 and 5 are how the setup learns from it.

  • template: The whole SaaS app, built from the libraries. Under construction. A codebase built from template comes with its Wardens built and turned on.
  • Foundry: The workspace around your agent. Under construction. Foundry pairs with Kingdom; the pairing is a Signet. Foundry sends every session to Archive. Your agent runs inside Foundry, on your own subscription.
  • Your agent: Claude Code or Codex, on the subscription you already pay for. Your agent runs inside Foundry, on your own subscription. Wardens notice what a request touches and remind your agent of what your project already has, and where it's written down; your agent decides what to use.
  • Wardens: Small agents inside Foundry, each holding one part of what your project knows. Under construction. Wardens are built from your codebase's docs, one per topic. Wardens notice what a request touches and remind your agent of what your project already has, and where it's written down; your agent decides what to use. Oracle checks whether a correction stuck and proposes changes to the docs and Wardens. A codebase built from template comes with its Wardens built and turned on.
  • Your codebase: Your code, and the docs and rules that say how it's done. Wardens are built from your codebase's docs, one per topic.
  • Archive: Keeps every agent session. Foundry sends every session to Archive. Oracle reads the sessions Archive keeps.
  • KCP: Runs your CLIs through Kingdom. Under construction. KCP will run your provider CLIs through Kingdom (in progress: it signs in today).
  • Kingdom: The permission hub. Closed source. Under construction. Foundry pairs with Kingdom; the pairing is a Signet. KCP will run your provider CLIs through Kingdom (in progress: it signs in today). Teammates and their agents use your integrations through a Signet. Your integrations connect to Kingdom, which holds their credentials. Artifactory will sign in with Kingdom (planned).
  • Signet: A revocable pass on the owner's terms.
  • Your integrations: GitHub, Slack, Linear, Google. Your integrations connect to Kingdom, which holds their credentials.
  • Teammates and their agents: Anyone the owner gives a Signet. Teammates and their agents use your integrations through a Signet.
  • Artifactory: Sharing what agents make, signed in with Kingdom. Planned. Artifactory will sign in with Kingdom (planned).
  • Oracle: Measures whether a correction stuck. Closed source. Oracle reads the sessions Archive keeps. Oracle checks whether a correction stuck and proposes changes to the docs and Wardens.
The other pieces

Also in the agentic tools.

agent-session runs each Claude Code and Codex session, and Archive keeps every one, for Foundry and Oracle alike.

Archive

MIT

Keeps a copy of every conversation with your agents on your computer, and copies it where you choose.

agent-session

MIT

Keeps Claude Code and Codex running between messages, so a tool can hold a long conversation with them.

hivemind

MITPaused

Lets several agents coordinate through a shared log. Not recommended for use.

Agentic building blocks

Pieces you can use on their own.

The parts of the agentic tools that stand alone, each an MIT package you can build on.

Signet

MIT

A pass you give someone, or something, to use one of your connected accounts. You set its limits, you can take it back, and every use is recorded. The package holds the protocol: keys, proofs, pairing and the client that presents a Signet.

KCP

MITIn progress

Runs your command-line tools through Kingdom so no token sits on your computer. It is the Kingdom CLI Proxy. Signing in works today; running commands through Kingdom is in progress.

foundry-core

MIT

The engine under Foundry, usable without it: context layers, agents, middleware, signals, threads, a harness and tracing, with no external dependencies.

benchResults from June 2026

Do I Still Have a Job?

Our own challenge set for coding agents, from staff to architect level. More challenges are coming.

bench.inixiative.com →