● WebMCP checking● Local Bridge offlinerev 0Working…
The shortest safe path from request to verified change
Open a safe copy. Ask for a change. Review the evidence and exact diff.
DELTA gives a WebMCP-compatible AI only the tools needed for the current step. Your original files stay untouched while you inspect related files, approve the exact proposal, and verify or roll back the result.
1
Open safe copySelect a project without giving write access to the original
2
Describe the changeSay the result you want in plain language
3
Review and approveCheck the exact diff and verification result
Step 1 · Recommended
Start safely with a project copy
DELTA analyzes a browser copy. Your original folder cannot be changed, and every proposed edit remains visible before approval.
The contest demo uses this safe, browser-based workflow.
Need to change real local files? Open advanced project methods
These methods are optional. Opening DELTA in a normal Chrome tab does not automatically connect that tab to Codex. Use a method only when its stated host requirement is satisfied.
External Chrome / Edge
Writable local folder
Gives this page direct read/write permission to one folder you select. It does not add an AI connection by itself.
Checking whether this browser can open writable folders…
Compatible AI host only
Agent Native
Uses native file tools already provided by Codex or another compatible AI host. Selecting it does not create those tools or connect an unrelated browser tab.
Optional local program
Native Bridge
Pairs DELTA with a separately running local Bridge for disk transactions, Git status, and Node or game-engine checks.
Be specific about the old value, new value, and anything that must stay unchanged.
DELTA first finds related files. It does not write anything at this step.
Change safety and file target
Optional verification contract
Agents can fill this through WebMCP. Humans may also declare exact checks here. Automatic modes will not claim success without deterministic criteria.
Codex / AI host project
Project connection required
DELTA can analyze this project, but the AI host must confirm the exact project before real files can be changed.
01Understand requestWhat should change
02Find related filesEvidence and impact
03Review changesExact before and after
04Check resultTests and rollback
One state, two interfaces
The person and the agent work on the same visible project state.
When an agent searches evidence or creates a preview through WebMCP, the result appears here. When a human changes execution policy or grants approval, the agent receives the updated state.
Next: open a project using one of the two choices above.Next: describe the change and select “Find related files”.Next: search wider or enter an exact project path to find usable files.Next: review the related files DELTA found.Next: open “Review changes” and approve the exact preview.The result is ready. Open “Result” to see what passed.
⌁
Evidence engine
Ranks paths, symbols, headings, text, imports, resources, Unity GUIDs, tests, and documentation links without sending the whole project.
◈
Controlled autonomy
Review First, Smart Auto, and Full Auto remain bounded by human policy, risk scoring, exact hashes, and protected-file rules.
✓
Proof, not promises
Task-specific assertions, structured syntax, native checks, and committed preview hashes decide whether work is complete.
Step 2 · Related files
These are the files connected to your request.
DELTA shows why each file was selected before any change is prepared.
WAITING
Evidence recovery
No evidence found
NOT READY
DELTA will not present a task as ready when no usable evidence was found.
DELTA will re-run the search using this exact path. The path must still pass current evidence and safety rules.
Evidence Lock
Work only from current evidence
NOT LOCKED
Start a task to lock the exact hashes used for planning.
Ranked assets
0
Start a task to select evidence.
Success contract
0
The agent or human must define deterministic success criteria before completion.
Bounded context slices
0 B
No context has been selected.
Project graph
See dependencies and dependents before changing files.
Edges include source, type, confidence, and reason so the agent does not treat every guessed relationship as equally certain.
Task impact
Start a task to trace impact.
Graph summary
Step 3 · Review
Review the exact changes before they happen.
Red lines are removed; green lines are added. Approval applies only to this exact preview.
NO PREVIEW
No change preview exists.
Human control
Review required
This change reached a human-defined safety boundary.
Create an exact change manually
Result
See what passed, failed, or was not run.
DELTA never presents an unverified result as complete.
NOT RUN
Apply or validate a change to see evidence.
Completion Proof
Cryptographic audit digest
NOT GENERATED
A proof is generated after validation from the task contract, locked evidence, committed hashes, validation gates, and measured activity.
Audit trail
Every human and agent action stays visible.
Tool calls, scope extensions, previews, approvals, writes, checks, validation, and rollback are recorded.
Workspace activity
No activity yet.
WebMCP invocations
No tool calls yet.
Multi-Agent Handoff
Continue the same task with another compatible agent
NONE
The capsule contains bounded task context and integrity evidence, never approval tokens, Bridge bearer tokens, or increased autonomy.