Agent report
Useful finding
Your agent completed a bounded task and returned a schema-checked report. It can guide work, but it does not verify itself.
Reliability for Codex & Claude projects
Keep your project and model account where they are. Ask Codex or Claude normally; i2x gives the agent bounded work, checks the returned result, and shows you what is proven, uncertain, or waiting for approval.
● In development · local product preview
BuildExpected 0 · actual 0
verifiedAuthorizationWrong user denied
verifiedPersistenceReading stored result
runningBetween “done” and dependable
Codex or Claude can turn an idea into working software. Then the difficult questions arrive.
i2x makes those questions one visible, repeatable workflow.
One project. One continuous story.
Choose a stage to see what you see, what the system commits, and how failure returns safely to the workflow.
01 / 06
i2x maps supported code, dependencies, declared flows and limitations before anything is changed.
No blurred meanings
i2x keeps three truths separate so a green badge cannot promise more than the evidence supports.
Agent report
Your agent completed a bounded task and returned a schema-checked report. It can guide work, but it does not verify itself.
Evidence receipt
The result binds source, environment, expected and actual values, checks, exclusions and provenance under one digest.
Current assurance
A certified runner produced passing, still-current evidence for the exact revision. Expiry or changed source removes the claim.
Bring your subscription
Use your own Codex or Claude subscription through its official client. A revocable workspace connector gives the agent bounded i2x tasks; i2x does not resell model access or take over your provider account.
An honest boundary: i2x can prove the connector round trip works. It cannot see your provider plan or remaining allowance.
[mcp_servers.i2x] command = "node" args = ["i2x-mcp"] [mcp_servers.i2x.env] I2X_CONNECTOR_TOKEN = "••••••••"
Choose how you work
You keep using the tools you know. i2x gives each request a project boundary, tells the agent exactly what it may do, and returns a result that separates the agent’s report from independently checked evidence.
Best when your project is a folder on Windows, macOS, or Linux.
Best for GitHub, GitLab, Bitbucket, a private Git server, or your CI pipeline.
Best when your web app, CLI, automation, or agent already owns the user experience.
Project access, credentials, network permission, source version, and final approval.
Project-specific reasoning and coding through the subscription or account you chose.
Scopes the work, applies the required checks, records lineage, and labels what is—and is not—verified.
Important: connecting i2x does not give an agent permission to approve its own result, publish software, or start recovery. Those effects remain separate and require your approval.
You choose the boundary
Start with one simple decision: where should your code stay? i2x adapts around that choice. You do not need to move your repository, buy a VPS, or give i2x more access than the work requires.
Code and credentials stay on your computer. Codex or Claude works through the local runner.
Your computer → local runner → governed resultSelect a repository and choose read-only analysis or a read-write worktree.
Git repository → chosen runner → governed resultRun i2x in your VM, container, development environment, or CI pipeline.
Your infrastructure → your policy → governed resultGrant revocable access for isolated execution without buying or managing infrastructure.
Scoped access → isolated runner → retained evidenceKeep the source offline and export a content-bound package for verification.
Offline project → evidence package → portable verificationWindows · macOS · Linux · CI and remote runners · web control from iOS and iPadOS
What every customer gets: connect the project in the way that fits your environment, let Codex or Claude build a readable system map, identify behavior that must not break, run bounded checks, and see clearly whether each result is an agent report or independent evidence. You choose the project boundary, credentials, network access, and read-only or read-write permission. Access is project-scoped and revocable; release and recovery always require separate human approval.
The operating model
Every plan, task and receipt is bound to the project, tenant and exact source—not a generic AI conversation.
Deterministic controls enforce coverage, evidence, authority and state transitions. Agent confidence is never the policy.
Release and recovery require current evidence, exact scope and fresh human approval before any supported external effect.
Redacted, recurrent outcomes may propose a revision. Evaluation, consented canary and rollback come before promotion.
Pricing
See exactly what each plan includes. Every plan keeps model access separate: use your own Codex or Claude subscription.
| Capability | Free$0Local | Personal$19 / monthUp to 10 projects | Shared$49 / monthUp to 500 projects |
|---|---|---|---|
| Project access | |||
| Local folders on Windows, macOS and Linux | ✓Included | ✓Included | ✓Included |
| Codex or Claude subscription connector | ✓Included | ✓Included | ✓Included |
| Read-only or read-write project access | ✓Your choice | ✓Your choice | ✓Your choice |
| Git repository connection | —Not included | ✓Included | ✓Included |
| CI, server and remote-runner modes | —Not included | ✓Included | ✓Included |
| Offline evidence package | ✓Included | ✓Included | ✓Included |
| Understanding and protection | |||
| Readable project system map | ✓Included | ✓Included | ✓Included |
| Protected behavior plan | ✓Included | ✓Included | ✓Included |
| Governed specialist-agent workflow | ✓Included | ✓Included | ✓Included |
| Failure handoff and bounded repair loop | ✓Included | ✓Included | ✓Included |
| Evidence and assurance | |||
| Locally reported results | ✓Included | ✓Included | ✓Included |
| Portable evidence export | ✓Included | ✓Included | ✓Included |
| Independent hosted verification | —Not included | ✓120 min / month | ✓600 min / month |
| Retained evidence storage | —Local only | ✓1 GiB | ✓5 GiB |
| Release and recovery evidence gates | —Not included | ✓Included | ✓Included |
| Workspace control | |||
| Project capacity | ✓Local projects | ✓Up to 10 | ✓Up to 500 |
| Personal activity history | ✓Local | ✓Included | ✓Included |
| Workspace members and roles | —Not included | —Not included | ✓Included |
| Shared approval and audit trail | —Not included | —Not included | ✓Included |
i2x · intelligence to execution
A reliability layer for newcomers who want to keep improving what they built—without pretending every agent answer is proof.
Walk through the product ↑