Skip to main content

Use Cases

connector.json + PTY-for-AI adapts to how you actually work.

Solo Developer: Multi-Model Workflow

One person. One machine. Multiple AI models for different tasks.
Why: Opus for hard thinking ($$$). Codex for a second opinion ($$). Haiku for grunt work ($). One person gets the output of a three-person team.

Pair Programming: Two AI, One Codebase

You and two AI agents working the same feature in real-time.
Why: Builder doesn’t review its own code. Reviewer catches mistakes in real-time, not after the PR.

Small Team: Shared AI Infrastructure

3-5 developers. Each has a laptop. One shared server.
Why: The server runs 24/7 Codex that reviews every push. Developers get feedback without waiting for human reviewers. The AI reviewer never sleeps, never forgets to check.

Open Source: CI/CD AI Agent

Automated PR review and triage for open source projects.
Why: Haiku triage costs pennies. Most PRs stop at phase 1. Only auth-related PRs get expensive Opus review. Cost-proportional to risk.

Remote Work: Follow-the-Sun

Team across time zones. AI keeps working when humans sleep.
Why: The pipeline spans time zones. When Seoul sleeps, SF verifies. When SF sleeps, Seoul reviews. AI doesn’t sleep at all.

Data-Sensitive: Air-Gapped Analysis

Data that cannot leave the building. AI comes to the data.
Why: Patient data never moves. AI runs where the data lives. Only aggregated, anonymized results travel. HIPAA/GDPR compliant by architecture, not by policy.

GPU Farm: Hardware-Optimized Deployment

Different hardware for different models.
Why: Laptop for coordination (free). GPU servers for heavy lifting (local, no API cost). Claude only for final integration (minimal API spend). Total API cost: ~2insteadof 2 instead of ~50.

Startup: Rapid Prototyping

Move fast. Try everything. Keep what works.
Why: Three different AI agents prototype three different architectures in parallel. Then three different AI agents debate which one to ship. Then one builds it. One hour instead of one sprint.

Enterprise: Governed AI Deployment

Full control. Full audit. Full compliance.
Why: Phase 1 uses local LLM with no network — customer data can’t leak. Phase 2 uses Claude but only sees anonymized summary. Sandbox ensures no file writes outside worktree. Every keystroke logged for audit. The AI is powerful AND governed.

The Pattern

Every use case is the same infrastructure: