Tul-KI Apply for private pilot
For AI agents touching production code

Approve the exact diff, not the agent.

Tul-KI fingerprints each risky agent action, checks policy, requests approval when required, and issues a signed Action Receipt that downstream gates can verify before they accept the change.

Apply for private pilot $ pip install tulki free CLI ▶ See an Action Receipt →
Action Receipt signed
diff_hashsha256:a1b2c3d4e5f6...
policyregulated-coding-v1
approverplatform-security
accepting_systemdownstream_gate
AI Agent
Pilot entry points
Repo / PR
CI / deploy
API / webhook · future
MCP tool call · future
Signed
Receipt
Accepting
System
Works above the agent: Tul-KI evaluates and records clearance for the change, not the chat tool.
Claude Code Codex Cursor Copilot Devin Windsurf

Policy for risky surfaces

Configure which paths and actions need clearance: auth, billing, infra, CI, secrets-related files, and deploys.

Approve the exact diff

Each Action Receipt binds approver, policy, changed paths, and diff hash. Change the code and clearance expires.

Proof that travels

Verify the same receipt in PR checks, merge rules, pilot deploy checks, or other acceptance points.

How exact-diff clearance works

1

An agent proposes a change

Tul-KI fingerprints the diff and reads the affected paths, workflow, and policy context.

2

Policy decides the next step

Configured low-risk edits can pass. Teams can pause sensitive paths and actions for approval.

3

A receipt unlocks the next control

The signed receipt is valid only for that diff, so modified or stale changes must be cleared again.

$ pip install tulki
$ tulki audit --repo you/repo
agent-authored merges: 12 / 87
merged on stale approval: 5
❯ _
Free CLI · pip install tulki

Ask your own merge history first

The free CLI is the local, advisory layer: tulki audit reads your merged PRs with your own read-only GitHub token and reports how many were agent-authored and how many merged on an approval given before the agent's final push — so the approver never saw what shipped. tulki doctor scans readiness and MCP posture, tulki policy init generates a starter policy from your repo layout, and tulki hook adds an advisory guardrail to your own coding agent. Everything runs on your machine; nothing goes to any Tul-KI service. The enforcement gate below stays in the private pilot.

Clearance scenarios

One decision, verified wherever the change moves.

Tul-KI checks the receipt against the current diff. It does not trust a PR title, branch, or stale approval; if the diff changes, clearance no longer applies.

Tul-KI Clearance CheckAction required
● billing/refunds.py sensitive_path

No valid Action Receipt found for this exact diff.

diff_hash: sha256:a1b2c3d4e5f6...
policy: regulated-coding-v1
Design partner program

Bring us your riskiest agent-written changes

We’re looking for teams already using AI coding agents on production repos. In the pilot, we’ll map your risky paths and actions, write the first policy, and wire exact-diff receipt checks into one current acceptance point, usually a GitHub PR check or deploy gate.

We’ll use this only to follow up about the Tul-KI design partner program. Protected by Cloudflare Turnstile.