Player profile
Parallel Code
An open-source desktop workspace for dispatching, monitoring, reviewing, and merging parallel coding-agent work across isolated git worktrees.
Profile
Where it fits
Parallel Code is an MIT-licensed desktop app for orchestrating multiple AI coding agents from one local interface. It supports Claude Code, Codex CLI, Gemini CLI, GitHub Copilot CLI, and other terminal-based coding agents.
Each task runs in its own git branch and worktree so agents can work concurrently without conflicting with one another. The app embeds real terminals, tracks task status, surfaces diffs, and helps review or merge completed work.
It belongs in Open Orchestrators because the product is directly about parallel coding-agent execution, worktree isolation, task coordination, review, and local operator control.
Builder web analytics
Measure projects built with Parallel Code
Parallel Code helps builders run several coding agents against isolated worktrees. Agent Analytics measures whether the shipped branch, docs update, onboarding change, product surface, or growth experiment improved user behavior after merge.
Instrument the deployed surface affected by the merged worktree. Agent Analytics reads product and web events after the Parallel Code-managed change ships; it does not replace terminal logs, git diffs, or agent transcripts.
First loop to measure
- a builder uses Parallel Code to run multiple coding agents against a feature, docs update, onboarding path, app surface, or growth experiment
- the selected worktree is reviewed, merged, and deployed
- the changed surface reports visits, sources, CTA clicks, signup, activation, retention, or task-completion events to Agent Analytics
- a follow-up agent fetches Agent Analytics results and turns user behavior into the next task or experiment
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including Parallel Code-managed page, docs path, traffic source, CTA click, signup, activation event, retention signal, or shipped experiment. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which Parallel Code-managed page, docs path, traffic source, CTA click, signup, activation event, retention signal, or shipped experiment moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.