project
One durable scope
A repository or folder, its connections, tasks, sessions, and launch configuration—kept together without hiding the filesystem.
project → tasks + sessionstermloop · native control room for coding agents
Keep every coding agent in the loop
TermLoop puts tasks, worktrees, real terminals, diffs, and agent coordination in one native workspace—without replacing Claude Code or Codex.
available nowopen sourceyour subscriptionsno telemetry
Ask To
Get a second opinion without copy-paste.
Ask one agent to consult another agent. TermLoop creates a visible helper Session, preserves the relationship, and returns the answer to the requester.
How to use Ask To
- Open Agents > Ask to and choose a provider for the second opinion.
- A visible helper Session receives the question and context.
- The answer returns to the requesting agent.
tree project
Simple objects. Serious workflows.
Projects hold the durable scope, Tasks describe work, and Sessions are the live agents and terminals operating inside that Project.
task
Work with optional isolation
A Task can stay lightweight or get one managed Git worktree when the work needs its own branch and checkout.
task → 0..1 worktreesession
Every process stays visible
Claude, Codex, terminals, and dev runs stay Project-scoped. Select them, refresh them, fork context, or coordinate them directly.
session → agent | terminal | run6 essential workflows
See the work stay connected.
A second opinion, a handoff, a fresh direction, and the tools to finish the change. Recorded in a working Launchpad demo Project.
Handoff
Move context to the agent already in the work.
Send a visible, composed handoff from one running Project Session to another. The target receives the brief in its own real terminal and continues from there.
How to use Handoff
- Open Agents > Handover to and choose an existing Session.
- The current agent composes the request, findings, and next action.
- The destination receives the handoff in its own terminal.
Session Fork
Explore another direction in a real terminal.
Fork a Session from the sidebar, see the parent-child relationship, and continue in a new Ghostty terminal. The branch in thinking is explicit instead of becoming another anonymous tab.
How to use Session Fork
- Choose a conversation to explore in a new direction.
- Fork it from the Session menu.
- Continue in a separate Session with visible parentage.
Tasks
Keep the goal beside the work.
Keep a clear brief, acceptance criteria and a small checklist attached to each Task.
How to use Tasks
- Open the Task beside the real project tests.
- Read the goal and acceptance criteria.
- Mark completed checks without losing the Task context.
Task Worktrees
Give each change its own workspace.
Create a branch and managed worktree directly from a Task. Keep parallel changes in separate checkouts.
How to use Task Worktrees
- Choose Create worktree on the Task.
- Name a new branch and choose its base.
- The Task now has its own branch and worktree.
Code review
Review changes where they happened.
Read the diff, compare versions side by side and keep track of the files you have checked.
How to use Code review
- Open the changed files in the Project.
- Use Full file and Split to compare code with its context.
- Mark files reviewed and revisit them from the reviewed list.
product principles
The terminal stays real. The workflow gets better.
--no-replacement-agent
TermLoop launches the Claude and Codex CLIs you already trust and pay for. It never proxies or imitates them.
--no-hidden-filesystem
Branches, worktrees, processes, and files remain ordinary local resources you can inspect outside the app.
--no-mystery-prompts
TermLoop-authored prompts are visible assets. Secret values stay out of durable state and public evidence.
--no-fake-coordination
Agent-to-agent requests, handoffs, terminals, diffs, and lifecycle changes are real product actions.
straight answers
Frequently asked.
Which agents does TermLoop support?
The first-class agent launch paths are Claude Code and OpenAI Codex, alongside ordinary terminal and dev-run Sessions. TermLoop uses your existing provider sign-ins rather than proxying model traffic.
Does every Task create a worktree?
No. A Task can have zero or one worktree. Create the Task to track work; provision a managed checkout only when branch isolation is useful.
Can multiple agents write in the same worktree?
Yes. TermLoop does not impose a product-level write lease or artificial launch gate. You choose whether agents share a checkout or work in isolated Task worktrees.
Where do my code and credentials go?
Your code remains on your filesystem. Agents connect directly to their providers. TermLoop keeps secrets out of durable product state, logs, URLs, and generated evidence.
Which desktop platforms are available?
The current public desktop download is for macOS. TermLoop Next treats macOS, Linux, and Windows as release gates; broader availability follows verified native builds rather than an untested compatibility claim.
Is the mobile connection real?
Yes. The companion pairs with a running desktop instance for Project visibility and terminal input. The public demo intentionally masks the one-time QR payload.
Is TermLoop open source?
Yes. The public source and releases are available on GitHub, including the terminal and agent-workflow layers.
ready when you are
More agents. Less terminal babysitting.
Download TermLoop and keep the whole engineering loop visible.