feat: Add Isolate kit

[Dhruv2mars]

Problem

Open-source maintainers often receive bug reports that describe a symptom but omit reliable reproduction steps. Isolate turns those vague reports into evidence that maintainers and coding agents can verify.

What this adds

• A Lamatic Supervisor flow for investigating public GitHub issues
• An authenticated HTTP MCP runtime deployed on Vercel
• Disposable Daytona sandboxes with immutable commit checkout support
• Deterministic probe evaluation with separate stdout, stderr, exit-code, and duration evidence
• A strict reproduction gate: two passing candidate runs plus a rejecting control
• Automatic sandbox cleanup after failed clones and completed investigations
• A controlled public testbed and vague issue for repeatable demonstration

Trust boundary

Lamatic owns investigation and orchestration. The external runtime owns execution and evidence. The model cannot self-certify a reproduction: only the deterministic certify_reproduction tool can return reproduced.

Verified

• Authenticated MCP discovery and tool calls against the live Vercel deployment
• Real Daytona sandbox creation, public repository clone, and cleanup
• End-to-end certification against the public testbed
• Candidate behavior reproduced twice
• Patched control rejected the candidate assertion
• 17 unit/integration tests passing
• TypeScript check and production build passing
• AgentKit structural validation passing
• No credentials committed

Current Lamatic platform finding

Lamatic Studio successfully discovers all five tools through the saved authenticated MCP connection. Both the standalone MCP node and direct MCP attachment to an AI node currently fail inside the Studio executor with Code generation from strings disallowed for this context. The same deployed MCP endpoint completes the real Daytona reproduction end to end outside that executor, isolating the remaining failure to the Lamatic execution environment rather than the submitted runtime.

Live resources

• MCP endpoint: https://isolate-agentkit.vercel.app/api/mcp (authentication required)
• Testbed: https://github.com/Dhruv2mars/isolate-cli-testbed
• Demonstration issue: Greeting command changes capitalization in names Dhruv2mars/isolate-cli-testbed#1

Status

Draft while the Lamatic Studio execution path and final walkthrough are completed.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a9fda9a1-48e3-46b6-b20b-98b1479d656d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

:robot_face: AgentKit Structural Validation

New Contributions Detected

• Kit: kits/isolate

Check Results

Check	Status
No edits to existing kits	✅ Pass
Required root files present	✅ Pass
Flow .ts files present	✅ Pass
lamatic.config.ts valid	✅ Pass
No changes outside kits/	✅ Pass

---

🎉 All checks passed! This contribution follows the AgentKit structure.

[github-actions]

Failure recorded at 2026-07-24T10:48:07Z UTC. If this PR is not fixed within 4 weeks it will be automatically closed.

[Dhruv2mars]

@codex review