Demo
Public walkthrough
The portfolio uses the public YouTube walkthrough for Switchboard so the repo stays lightweight and pushable. The local high-resolution export is intentionally not part of the git build.
Flagship
VS Code Extension
Multi-Agent Orchestration
Switchboard
Positioning: a coordination layer for vibe-coding tools. Connect Codex, Cursor, Claude, and Gemini, elect exactly one Leader, assign the rest as Workers, and run the entire workflow from one chat surface inside VS Code.
Switchboard is built for the real pain of agent-heavy development: hopping between providers, losing memory across sessions, repeating context, manually re-framing prompts, and debugging work you cannot fully see.
Workflow Preview
User Thread
One conversation surface. No duplicated prompting across tools.
Leader
Plans work, decomposes scope, routes sub-tasks, merges outcomes.
Worker 1
Refactor
Worker 2
Tests
Worker 3
Docs
Diff Tracking
See exactly which files changed and where work moved.
Thread Memory
Resume without restating your repo, history, or intent.
Why This Matters
Demo strategy
- Public viewers get a stable, browser-friendly walkthrough.
- The portfolio repo stays compatible with standard GitHub pushes.
- The case study still shows the core product model, UX, and orchestration flow in detail.
Problem
Coding agents are powerful, but fragmented.
- Developers bounce across Codex, Cursor, Claude, and Gemini because each one is strong at different tasks.
- Memory is inconsistent across sessions, so context gets repeated and tokens get burned restating repo state.
- Prompt engineering becomes manual routing work instead of product work.
- There is no clean orchestration layer to inspect decisions, file diffs, or task delegation.
- Debugging multi-agent runs is weak because you cannot see the full execution path in one place.
Solution
One Leader. Multiple Workers. Shared state.
- Users connect their preferred providers once and assign exactly one Leader.
- The Leader owns planning, task decomposition, and worker routing.
- Workers receive the right scoped prompts for their specialty instead of full-thread overload.
- Switchboard persists thread history, remembers prior work, and exposes file-level diffs and workflow trees.
- The full system lives inside VS Code, so coding, inspection, and continuation happen in one environment.
How It Works
Execution flow
Connect providers
Bring your existing agent stack into one extension instead of choosing a single locked-in tool.
Assign the Leader
Exactly one Leader owns the thread, planning logic, and delegation model.
Talk once
The user chats only with the Leader. No manual fan-out across tools.
Route sub-tasks
The Leader breaks scope into targeted prompts and sends each one to the best Worker.
Track diffs + workflow tree
Every file mutation and routing branch is visible, so debugging is no longer blind.
Resume later
Threads remain resumable with stored history, preserving intent and eliminating repeated setup cost.
Feature Grid
Core product surfaces
The value is not just multiple providers. The value is orchestration, visibility, and continuity wrapped in a clean editor-native workflow.
Leader/Worker Model
Strict orchestration hierarchy so planning and execution responsibilities stay legible.
Provider Connections
Bring in the agents you already trust instead of rewriting your workflow around one vendor.
Persistent Memory
Resume threads with context intact, including previous decisions, file state, and task intent.
Real Diff Tracking
Inspect exactly what changed and which agent path contributed to the edit.
Workflow Trees
Visualize branching execution so debugging and trust improve with more agents, not less.
Resumable Threads
Treat multi-agent sessions as continuing work units instead of disposable chat windows.
Workflow Visualization
Built for auditable execution
Switchboard is not just another chat pane. It is an orchestration surface that shows where a plan started, how it split, which workers touched which files, and how the thread can resume without losing state.
Thread Root
"Refactor auth flow, preserve tests, summarize diff."
Leader Plan
Auth split, test preservation, docs update.
Worker Route
Send code rewrite to strongest editing model.
Review Path
Ask another worker to inspect regressions.
Diff Tree
Visible changed files, patch trace, and merge result.
Resumable State
Thread can be reopened later without reloading context from scratch.
Tech Stack
Core stack
VS Code API
TypeScript
Node.js
Extension Host
Provider SDKs
Prompt Routing
Thread Storage
Diff Tracking
Workflow Graphs
Design principle
Agent UX should feel like a coordinated system, not a folder of disconnected chat tabs.
Outcome
What Switchboard improves
Lower token waste
Repeated setup context gets replaced by resumable threads and shared state.
Cleaner debugging
Workflow visibility and diff trace make agent behavior inspectable instead of opaque.
Better specialization
Each provider can do the work it is best at without the user manually coordinating every handoff.
Stronger continuity
Sessions survive longer than a single chat window, which matters for real engineering work.