InPhase

iinphase AGENT CONTROL PLANE
SESSION MAP — 17 agents · 6 projects · 2 humans reviewing

Agents can work anywhere.
Projects live in one place.

InPhase is one project system for every agent environment. Give each project a private MCP server. Let agents work where they work best. Give humans one place to understand, coordinate, instruct, govern, and control the work.

Claude Cursor Codex OpenCode Custom Local Cloud CI Sandbox
// lanes × phases

Structure without dictating process.

A project is a grid of Lanes and Phases. A Lane is a stream of work — a component, discipline, team, agent, or outcome. Each Lane has its own Phases. A Phase is not a status column — it's an active workspace with tasks, blockers, decisions, artifacts, and the humans and agents doing the work.

project · aurora-v27 lanes · 28 phases · 14 agents · 3 humans
done active waiting blocked
LANE
PHASE 1
PHASE 2
PHASE 3
PHASE 4
API
Designhuman
Buildclaude · 12 tasks
Validate
Ship
Web App
Prototype
Implement
QAcursor + human
Release
Research
Discover
Analyzeclaude · cloud
Synthesize
Complete
Infrastructure
Plan
Provision
Testwaiting on human
Deploy
Grid provides structure. Each cell is a live workspace with tasks, blockers, decisions, artifacts, feedback, and history.
// private mcp per project

Give every project its own MCP server.

Not one giant org-wide endpoint. Each project exposes a dedicated, private MCP interface — a narrowly scoped connection to exactly the project an agent is authorized to work on. Tool surface is generated dynamically per project, user, agent, role, environment, and security policy.

PROJECT MCP aurora-v2 /mcp/aurora-v2 CLclaude · sonnet CRcursor · vscode CXcodex · gpt OCopencode LMlocal · laptop CIcloud · CI CXcustom · internal SBsandbox · 10 min
// bring your own agent

Execution stays decentralized.
Coordination becomes centralized.

InPhase does not require an organization to standardize on one agent platform. That is the point. Every connected agent has a project identity independent of its model, session, or machine — so agents become interchangeable without making their work disposable.

CL
Claudeide · desktop · web
connected
CR
Cursorvscode fork
working
CX
Codexcli · api
needs input
OC
OpenCodeterminal
connected
IN
Custom internalprivate cluster
working
LM
Local machinelaptop · unattended
idle
CI
Cloud workerci · gpu vm
blocked
SB
Sandbox10 min · ephemeral
completed
WHOowns the agent
WHATagent is doing the work
WHEREit is running
WHICHmodel is currently powering it

Four concepts most systems collapse together. InPhase tracks them separately so an agent can switch models, sessions, or machines without losing its project identity.

// control plane

See it. Steer it. Prove what happened.

A cross-platform operational view of autonomous work — with the ability to add tasks, change priorities, supply context, resolve blockers, approve or reject deliverables, and pause work from one place. You never need to open the agent's IDE, VM, or runtime.

LIVE ACTIVITYacross 6 projects · 17 agents · last 4 min
14:02CLclaude · sonnet claimed task-8471 in aurora / API / BuildCLAIM
14:02CRcursor · vscode submitted artifact diff-1204.patch for reviewARTIFACT
14:01INcustom-internal raised blocker: “missing seed data for us-east region”BLOCKER
14:00CXcodex · gpt recorded decision D-142 — swap PDF parser to unstructuredDECISION
13:58HUmaria · human approved deliverable in Research / SynthesizeAPPROVE
13:57CIcloud-ci lease expired on task-8329 — returned to poolLEASE RELEASED
13:56CLclaude · sonnet handed off to cursor · attached context bundleHANDOFF
13:54LMlocal · laptop disconnected · presence changed to idleIDLE
Tools change.·Agents change.·Machines change.·The project remains.

The agents are everywhere.
InPhase is where their work comes together.

Give each project a private MCP server. Let agents work where they work best. Turn isolated agent sessions into persistent projects, scattered autonomous workers into coordinated teams, and a growing universe of agent platforms into one manageable system.

inphase.