Create your i2x account
Verify your email, then set up a passkey to sign in.
Already have an account? Sign in
Sign in with email
Sign in with a passkey
Enter the account ID you saved when you signed up.
Recover your account
Local development access
Email verified
Get a sign-in link to open your workspace.
Workspaces
Open a workspace to add a project or connect Codex or Claude.
Workspace invitations
Only you can accept an invitation addressed to your i2x identity.
Sign-in settings
Manage your passkeys and devices signed in to i2x.
Account ID for passkey sign-in:
Save these recovery codes now
Each code works once. They will not be shown again. Store them somewhere separate from this device.
Signed-in devices
OpenAI access on this machine
Loading local account status...
Projects
Connect Codex or Claude
Inspect projects and run checks from Codex or Claude.
Add a passkey for extra security
Usage, people and activity
Usage and limits
See how much hosted time and storage this workspace has available.
People and activity
Manage access and see recent changes.
Audit history
Some project details couldn?t load. Try loading them again.
Overview
Status and approvals
This phone does not run project code. Review current status and grant only a displayed, bounded approval. Inspection, specialist work, verification, drills, release execution and recovery execution stay on the desktop or certified runner.
Project status
Get your project ready
How you work with i2x
Inspect the project to create a source-bound map.
What i2x currently understands about this project
See the system, evidence and change together
Inspect the selected project to create a source-bound component and lineage view.
Coverage, uncertainty and standards exports
Project inventory
Connections
Repository access
Choose where your project is and which coding assistant will open it.
Connect a Git repository
GitHub repository
Connect exactly one repository through your GitHub App installation. i2x requests repository contents and metadata read access only.
Bitbucket or self-hosted Git
Save repository identity only. Never paste an access token, password, SSH key or model credential here. The customer-side runtime supplies a credential only to the provider when a read is authorized.
Other environments
CI, customer servers and hosted runners appear here only after their complete setup and evidence paths pass acceptance testing.
Use i2x from GitHub Actions
GitHub runs the checks on the exact commit you approve. i2x verifies which repository, workflow and commit are running, then returns a governed receipt. No GitHub secret, model credential or repository write permission is given to i2x.
- Accept the checksReview the project verification plan in i2x.
- Commit the workflowDownload the stable YAML below and add it to your repository.
- Bind exact commitsTell i2x which workflow commit and source commit may run.
- Copy five variablesAdd the displayed non-secret values in GitHub repository settings.
- Run the workflowGitHub proves the job identity; the runner executes only accepted checks.
- Read the receiptSee the exact source, every outcome, limitations and next safe action.
Use i2x from GitLab CI
GitLab checks out the exact commit and issues a short-lived identity token for this job. i2x verifies the project, ref, pipeline configuration and source before accepting results. No personal access token, model credential or repository write permission is sent to i2x.
- Accept the checksReview the exact project verification plan in i2x.
- Include the jobDownload the stable YAML and include or merge it into
.gitlab-ci.yml. - Bind exact commitsRecord the source and top-level pipeline-configuration identities.
- Copy five variablesAdd the displayed non-secret values in GitLab CI/CD settings.
- Run the pipelineGitLab proves the job identity; the client executes only accepted checks.
- Read the receiptInspect the exact source, every outcome, limitations and next safe action.
Upload a source snapshot
Use this when the repository stays outside GitHub but an authorized i2x run needs an exact, temporary copy. The local runner excludes secret-like files, shows the exact source digest before transfer, and uploads only after you repeat that digest.
- Prepare locallyThe runner packages regular project files and excludes Git metadata, dependencies, build output, symlinks and secret-like filenames.
- Review the digestThe first command uploads nothing. Review its file count, size and exclusions.
- Confirm exact bytesRepeat the command with the displayed source digest. i2x encrypts the package at rest and binds it to one run and its current access choice.
- Automatic expiryThe package expires within seven days. You can delete it sooner below.
Who can access this project?
Work and results
Run queued governed work
Loading task operation status...
Your project, from access to decision
Loading the customer workflow...
Governance gates
Passing one gate grants only the next bounded step. It never silently grants verification or production authority.
Always separate: your coding agent reasons and proposes; checks produce evidence; you authorize consequential actions.
Project activity
Protected promises
Active workflow
Releases and recovery
Learning
Inspect latest proof snapshot
Timeline
What must keep working
Describe observable outcomes that must continue working.
Suggestions from your coding assistant
Agents may prepare work. A proposal does not approve, verify, release, or recover anything.
Issues and repairs
Accepted findings cite failed evidence. A repair consumes one of two attempts and remains unverified until the exact candidate passes a complete rerun. D6 reports show their evidence origin and never present agent hypotheses as proof.
Approved checks
Review the approved checks and what each one protects.
CI results
Review results reported by your CI service. Independent verification and approval for releases or recovery are separate.
Check results
These results come from checks run on your computer. Independent verification appears separately when available.
Activity
Project settings
Project name
Available features
This matrix distinguishes locally available work, currently certified hosted execution, control protocols, and unavailable provider effects. A protocol or approval is not delivery certification.
Feature verification
See which features have passed independent review for this version of i2x.
Release preparation
Prepared requests bind an exact artifact, target, run, and receipt. Approval never deploys by itself. A release is verified only after certified live-identity readback and required postchecks.
Recovery
You choose what may be restored. i2x binds that exact scope, requires a certified isolated drill, checks the result, and only then asks a separate human to approve one recovery attempt. An approval never restores anything by itself.
Governed skill canaries
Opt-in applies only to future coverage plans. Existing runs stay pinned. Allocation, evidence, rollback, and promotion are determined by policy and remain visible here.
Verify a decision proof locally
Select a downloaded decision bundle and a separately obtained i2x platform public-key file. Optionally add one continuity bundle or the dual-signed rotation records when your trusted fingerprint belongs to an older key. All files stay in this browser session and are not uploaded. Verification proves the historical decision and review binding—not that a release, recovery, repair, or other proposed effect occurred.
Verify project evidence locally
Select a downloaded evidence bundle. For independently signed runner evidence, also select a separately obtained i2x platform public key and enter its fingerprint from another trusted channel. The verifier separately checks work-generation governance, the result signature, deterministic runner-certification lineage, independent QA review, and platform identity. Files stay in this browser and are not uploaded. Authorization of a new work generation is not verification of its result.
Verify authenticated report evidence locally
Select a report bundle downloaded from mission control, a separately obtained i2x platform public key, and its fingerprint from another trusted channel. The browser recomputes the report relationship, verifies the outer platform signature, and verifies the bound runner signature, certification lineage and independent review. Files stay in this browser and are not uploaded. Current revocation still requires an online check. No result grants release or other effect authority.
Verify a complete customer-review proof locally
Select the complete review package, a separately obtained i2x platform public key, and its fingerprint from another trusted channel. The browser replays the immutable review, retention policy, authenticated report, runner lineage, fresh authenticity status, and outer package signature without control-database access. Files stay in this browser and are not uploaded. Verification grants no release, recovery, repository-write, or other effect authority.
Verify an emergency platform identity locally
An emergency replacement is a new identity, not a continuous rotation. Download or select the portable evidence, then compare its full fingerprint with one obtained through a separate trusted channel. The bundle and fingerprint stay in this browser session and are not uploaded.