Native desktop / Multi-provider / Proprietary

A proprietary command center
for supervised coding work.

Warden brings parallel coding sessions, approvals, plan progress, provider choice, spend, code intelligence, and persistent context into one native workspace. It is a working product now being hardened for a proprietary public binary.

Get public release updates Read the release update

native cockpit preview

 COMMAND CENTER PUBLIC RELEASE sessions active / waiting / blocked
approvals operator decision required
plan progress stays visible
cost per-session estimate
# One cockpit, many supervised coding threads.

Why multi-provider matters

Provider choice is configuration, not architecture.

POINT 01

Provider choice should stay visible.

Choose the service and model that fit the work in front of you.

Warden keeps supported provider choice in the operator’s hands without rebuilding the surrounding workflow.

POINT 02

Different work has different tradeoffs.

Compare capability, speed, context, and estimated cost deliberately.

The command center keeps the active provider and model attached to the session record, where the operator can see them.

POINT 03

One provider should not define the product.

Keep the operator workflow stable while providers change.

Current development builds cover multiple provider families. Exact support and transition behavior will be stated per public binary.

Provider availability

One command center, multiple provider families.

Current development builds connect Anthropic, OpenAI, and Gemini workflows behind the same operator surface. Release documentation will state the exact models, authentication paths, regions, and platforms validated for each binary.

Development coverage: Anthropic / OpenAI / Gemini
Public support matrix: published with each binary

Command center

Practical controls for supervised coding workflows.

Warden combines the everyday work of a coding agent with the controls needed to supervise it. Files, commands, plans, sessions, providers, connected tools, and spend stay in the same operator surface.

Read and edit files Run commands Review plans Manage sessions Connect MCP tools Inspect diffs Search the web Track cost Provider selection Context controls

Integration readiness

Use MCP tools, and let supported clients use Warden.

MCP client

Bring focused tools into the session

Current development builds connect compatible MCP servers alongside Warden’s native file, command, planning, and session workflows.

MCP server

Expose a controlled Warden surface

Warden can also present supported capabilities to connected clients. Public release notes will list the integrations and transports validated for each platform.

Operator controls

Supervision is a product requirement, not an afterthought.

Warden’s working product includes permission rules and approval controls that keep consequential tool use visible. Policies can distinguish routine reads from edits, commands, network activity, and other actions that deserve review.

Visible controls

review approval session controls

Apply the level of review that fits the session, then keep the decision in view.

Release boundaries

Permission behavior fails toward operator control when a rule cannot be resolved. The public binary will document the policy surface validated for that release.

Workflow controls

Keep automation visible to the person responsible for the work.

Development builds expose lifecycle events around tool use, decisions, and sessions. That gives operator-owned automation a place to inspect, notify, or block configured actions without hiding the decision inside the model turn.

Before tool use After tool use Approval decisions Session changes Operator notifications Workflow integrations

Long-running sessions

Long sessions need context controls, not silent amnesia.

Warden tracks session context and gives the operator a visible path to compact older turns while retaining the working thread. Exact thresholds depend on the active model and are part of release validation.

session context

// context pressure stays visible before compaction

Long-running work

Keep longer coding sessions useful as their context grows.

Context controls

Make context pressure and compaction behavior visible to the operator.

Operator visibility

See when a session is approaching the limits of its active model.

Release validation

Thresholds remain model-dependent and will be qualified per public release.

Built for deliberate operation

The operator should be able to see what changed.

The command center keeps session state, approval decisions, tool activity, and code changes in view. Release acceptance will define practical output limits without reducing the product to a trust-me summary.

Visible session state / visible decisions / reviewable code changes

Cost tracking

Make spend visible while work is in motion.

Current development builds keep estimated usage and spend attached to the session, with operator-set budget controls in the workflow. Provider billing remains authoritative, so public releases will state estimate and cap behavior for each supported provider.

warden /cost

 $ /cost Session cost ledger ─────────────────────────────────────────
active provider estimated spend
session budget operator controlled ───────────────────────────────────────── Total shown in session Budget controls: release-specific

Integrated context

Code truth, durable memory, and session context in one cockpit.

TheAuditor

Query code intelligence without leaving the session

Development builds bring TheAuditor’s focused code and security answers into the command center, so the operator can inspect the same facts available to the agent.

Curator

Carry current project memory into the work

Curator integration brings durable decisions and changed standards forward alongside the live session. Public releases will identify supported integration paths.

Session continuity

Find the session, understand it, continue deliberately.

Session records

Development builds persist searchable session records with the working directory, provider choice, tool activity, and conversation history.

Visible spend

Estimated usage and spend remain attached to the session instead of resetting the operator’s view of the budget.

Reviewable work

Search past work, inspect what happened, and return to the right project thread.

Release validation

Resume and recovery behavior is being validated end to end and will be qualified against each public binary.

Operator outcome

Less terminal hunting, more deliberate continuity

Warden’s native cockpit is built to make parallel work and past work legible from the same place, while keeping continuation under operator control.

Active development Working product Proprietary

Status & disclosures

A working product, with a public release still being prepared.

Warden is a working proprietary native desktop command center for multi-provider coding work. The public release is being prepared with a realistic two to three month horizon, and the supported binary surface will be documented before launch.

The public binary release is planned on a two to three month horizon.
Provider, model, integration, and platform support will be listed per release.
APIs and local data formats may change while release validation continues.
Warden is proprietary software. Its source code is not distributed.

The ecosystem

Better alone. Unfair together.

Five focused tools for shipping with AI agents. Each stands on its own; together they cover code, action, orchestration, memory, and proof.

TheAuditor

Don't let agents guess about your code.

theauditortool.com →

Warden

Keep AI coding work visible across supported providers.

you are here

Arbiter

The command center for your AI operation.

arbitermcp.com →