AI agents do more than suggest code. They run shell commands, read files, call services, change infrastructure, and interact with production systems.

Kontext puts local policy between AI agents and the tools they call. It observes supported actions, evaluates policy before consequential actions run, and records the decision and outcome in an authorization ledger.

Start in observe mode. See what policy would stop. Move supported boundaries into enforcement when you are ready.

Policy evaluation errors allow the tool call, including in enforce mode, and remain visible as failures in the activity record. Completed policy denies and unavailable required approvals still block. This error fallback does not change behavior when the daemon is unavailable or enforcement has no usable policy.

• Local decisions: policy evaluation happens alongside the agent.
• Pre-action enforcement: matching actions can be denied at supported synchronous hooks.
• No wrapper command: install Kontext once and continue using your agents normally.
• Attributable evidence: preserve the agent, session, action, policy decision, and outcome.
• Managed rollout: distribute policy and review redacted records across an organization.

Kontext currently supports Claude Code, Claude Cowork, and Codex. Exact event and enforcement coverage varies by agent—see the agent support matrix.

Managed Claude hooks recognize Cowork sessions with either full or shortened session directory names, preserving their Cowork identity in activity records.

Quickstart

Install Kontext

brew install kontext-security/tap/kontext

Connect this Mac

Create an install token in the Kontext dashboard, then run:

Setup:

• stores the install token in the macOS login keychain;
• installs hooks for supported agents;
• starts the local Kontext daemon;
• connects the installation to your Kontext organization.

Verify the installation:

Then keep using Claude Code or Codex normally. You do not need to launch the agent through a separate wrapper.

Self-serve setup currently supports macOS. Managed and cloud environments can run the same local runtime when they provide a supported hook contract, storage, and daemon lifecycle.

What changes after setup?

Without pre-action policy, an agent action executes before a security team can review its logs:

agent requests an action
        |
        v
action executes
        |
        v
activity appears in a log

With Kontext:

agent requests an action
        |
        v
Kontext receives it through a supported hook
        |
        v
local policy evaluates the action
        |
        +---- allow ----------> action continues
        |
        +---- would deny -----> action continues and evidence is recorded
        |                       (observe mode)
        |
        +---- deny -----------> action is stopped before execution
                                (enforce mode)
        |
        v
decision and outcome enter the authorization ledger

This creates a decision point before the action, not only a record after it.

Observe first. Enforce when ready.

Blocking every unfamiliar action on day one creates noise and interrupts developers. Allowing every action indefinitely leaves policy as passive monitoring.

Kontext separates rollout into two modes:

Observe mode

Observe mode records the policy decision without interrupting the agent.

Use it to answer:

• Which tools are agents calling?
• Which actions would current policy deny?
• Which repositories, files, and systems are involved?
• Where would enforcement interrupt legitimate work?
• Which event surfaces can actually stop the action?

Enforce mode

Enforce mode returns a real denial when a deterministic policy matches at a supported synchronous pre-action hook.

Policies can define boundaries around actions such as:

• destructive commands;
• sensitive-file access;
• production-system operations;
• credential access;
• data exports.

Enforcement is intentionally limited to event surfaces where the agent waits for Kontext before continuing. Kontext does not claim that receiving an event means it can stop every action from that agent.

Know what happened—and why

Every supported event that reaches Kontext can contribute evidence to the local authorization ledger.

A record can include:

• the agent and session;
• the lifecycle or tool event;
• the tool name and available input;
• the local policy decision;
• the policy responsible for that decision;
• the available action outcome;
• redacted evidence for later review.

Kontext records tool activity and decision evidence. It does not capture model reasoning or reconstruct full conversation history.

Managed deployments can export redacted records to the Kontext dashboard for organization-wide review, retention, and investigation.

Policy where the agent runs

The decision path stays local:

Claude Code / Cowork / Codex
              |
              v
        supported hook
              |
              v
     local Kontext runtime
              |
        +-----+------+
        |            |
        v            v
  policy decision   local ledger
        |
        v
 allow / would deny / deny

A hosted service does not need to answer every tool call.

Managed deployments add organization configuration, policy rollout, record export, identity, and retention. They do not move the synchronous decision path out of the agent environment.

Supported agents

“Supported” means more than accepting an event. Kontext documents which events it receives, which events can block, and how each integration is installed.

See the agent support matrix for exact behavior, deployment scope, and known gaps. It is the authoritative source for enforcement coverage.

Kontext and sandboxes solve different problems

A process sandbox asks:

Which files, network destinations, credentials, and operating-system resources can this process access?

Kontext asks:

Which agent is attempting which action, what policy applies, should the action proceed, and what evidence proves the decision?

Kernel sandboxes are strong containment boundaries. Kontext provides semantic policy and attribution at supported agent and tool hooks.

They are complementary:

Kontext
  decides whether the action is authorized
              |
              v
sandbox
  constrains what the process can physically access

Kontext does not claim kernel-level isolation. Use an appropriate sandbox when the threat model requires process, filesystem, or network containment.

Why not just collect agent logs?

Logs tell you what an agent reported after an event.

Kontext creates an authorization decision before supported consequential actions execute, then links that decision to the available outcome.

That distinction matters during:

• policy rollout;
• incident investigation;
• production-access review;
• developer exception handling;
• compliance and audit review.

The result is not only “the agent called a tool.” It is evidence of what was requested, which policy applied, whether it was allowed, and what happened next.

Run Kontext across your organization

Managed deployments add:

• centrally managed deterministic policy;
• enterprise identity and organization controls;
• observe-to-enforce rollout;
• managed agent and cloud deployment support;
• redacted evidence export;
• audit retention;
• deployment health and backlog monitoring;
• onboarding for security and platform teams.

For deployment planning and organization onboarding, contact [email protected] or book a conversation.

Diagnose an installation

doctor checks:

• installed agent hooks;
• daemon health and version;
• managed export health;
• pending export backlog.

It exits non-zero when a configured installation is unhealthy.

When a self-serve daemon is stale:

Rotate the installation token by running setup again:

Remove the self-serve installation:

kontext setup --uninstall

Data handling

• Policy decisions happen locally.
• Tool activity and decision evidence are stored locally.
• Sensitive values are redacted before local storage and managed export.
• Kontext does not store model reasoning or full conversation history.
• Managed deployments can export redacted records to the organization dashboard.

See the Guard documentation for the runtime and data boundary.

Development

go build -o bin/kontext ./cmd/kontext
go test ./...
go test -race ./...
go vet ./...

• Read SUPPORT.md for support channels.
• Read CONTRIBUTING.md before opening a contribution.
• Report vulnerabilities through our Security Policy.
• Kontext is released under the MIT License.

kontext report shows discovered agents and authority exactly as last accepted by the cloud. Use kontext report --json for the raw payload. Before the first successful send, it reports no data.

Set KONTEXT_AUTHORITY_SCAN=off in the daemon environment to disable authority collection and transmission on this Mac.