New Your agents keep walking after you quit

Every project is
its own trek.

No two journeys look the same. Trek gives every branch its own agent, so you can explore many paths at once and follow the one that leads somewhere.

$ trek-server add .
Pitch camp on Mac, Windows or Linux
Travel with Claude Code Codex Gemini Grok Ollama LM Studio

01Trailheads

Many trails. Walked at once.

Every idea gets its own path. Each branch is a git worktree with its own agents in a real terminal, all on one map. Break a new trail with +, pick one up from a pull request, and let five agents explore without crossing paths.

  • Where every trail stands: ahead, behind, uncommitted
  • Several repositories in one expedition
  • Run each trail's own dev stack on your Mac
  • Rest a trail, and pick its sessions back up later
acme-web 4 worktrees · 6 sessions
feat/checkout-v2Claude
⏺ Update CheckoutForm.tsx
⏺ Update useCheckout.ts
⏺ Bash npm run typecheck
  running…
fix/null-cartClaude
✓ 14 passed
Push and update PR #218?
❯ 1. Yes
  2. No
feat/promo-endpointCodex
• Added POST /promos/:code
• Wrote 6 handler tests
• Running go test ./promo/…
chore/node-22Gemini
✦ Bumped engines to node 22
✦ Updated CI matrix
✦ All checks pass.

02Signals

Know who's waiting at the fork.

Agents stop when the path splits. Trek watches every session: a tab pulses orange when an agent needs a decision, turns green when it reaches the end, and a notification brings you straight there, wherever you wandered off to.

  • A status dot on every trail, a badge on every tab
  • One bell lists everyone who needs you
  • Mark a trail complete to silence it
Notificationsacme
?
fix/null-cart
Claude is waiting on you
now
✓
chore/node-22
Gemini looks done
4m
feat/checkout-v2
Claude is working
12m
✓
docs/readme
Marked complete
1h
✕
spike/search
Process exited · Restart resumes it
2h

03Camp

The journey continues without you.

Every expedition needs a camp. Trek pitches one on your Mac, and trek-server sets one up on any Mac, Windows or Linux machine. Close the lid and walk away; your agents keep going, and Trek picks up right where you left them. Every window and every phone on a project sees the same sessions, live.

  • No account, no relay, no telemetry. Camp is yours
  • One token per traveller's device, revoke any time
  • Reach camp over Tailscale, your LAN or wss://
  • Runs on macOS, Windows and Linux, as a background service
devboxmacOS · Windows · Linux
laptop
trek-server
phone
# register the repos agents can work on $ trek-server add ~/repos/acme-web $ trek-server add ~/repos/acme-api # one token per device $ trek-server token add laptop $ trek-server token add phone # pitch camp $ trek-server

04Guides

Choose your guide for the terrain.

Different ground calls for different guides. Trek runs the real CLIs in a real terminal, not an SDK wrapper: Claude Code, Codex, Gemini, Grok, or a local model through Ollama or LM Studio. Slash commands, skills, plugins, hooks and permission prompts all work the way they do in your own terminal, and your subscription is used the same way too.

  • Local models welcome, through Ollama or LM Studio
  • Save session types with their own guide and briefing
  • Your CLIs, your logins, your config
New sessionfeat/checkout-v2
C
Claude Code
claude · acceptEdits
default
Cx
Codex
codex
G
Gemini
gemini
X
Grok
grok
L
Local
ollama · http://127.0.0.1:11434
on-device

05Expedition lead

One guide to lead the expedition.

The Global panel (⌘J) is a project-wide agent with Trek's own MCP tools. It breaks new trails across your repositories, sends guides down them, queues their next legs, reads their progress and waits for them to report back. When the route forks, it asks you to decide.

  • Queue the next leg for a session to start when it's ready
  • Tag, note and link a trail from a prompt
  • Tools stay on 127.0.0.1, scoped to the project
Global · Claudetrek-dev MCP
Fix TOW-420 and TOW-421 in their own worktrees, then tell me when both pass.
create_worktree fix/tow-420
create_worktree fix/tow-421
start_session fix/tow-420 · "Fix TOW-420…"
start_session fix/tow-421 · "Fix TOW-421…"
wait_for_sessions 2 sessions · until all
both done after 6m 12s
read_terminal fix/tow-420, fix/tow-421
set_worktree_tag fix/tow-420, fix/tow-421 · In Review
Both fixes are in and their tests pass. I tagged the branches In Review.

06Trail log

Every trail keeps its log.

Mark how far each trail has come: In Progress, In Review, Ready to Deploy. Pin its Linear issue and pull request, and leave notes for whoever walks it next. The log belongs to the branch, so it's still there when you come back to it.

  • Linear issue status and title on the chip
  • Filter the map by how far along each trail is
  • All Notes gathers every trail's log in one place
feat/checkout-v2In Progress
TicketTOW-412 One-page checkout
PR#221 Checkout v2 (draft)
Tag
Note
Waiting on design for the promo field. Keep the old flow behind CHECKOUT_V2.

07From anywhere Coming soon

Check in from the trail.

Trek for iOS and Android connects to your camp, so the journey comes with you. See where every agent is, answer the one waiting at the fork, and send it on its way from the coffee line, the train, or the actual trail.

  • The same live sessions as your desktop
  • A push notification when a guide needs you
  • Answer, queue a prompt, or start a new session

Join the waitlist

Which phone do you use?

One email when it ships. That's it.

Where will yours lead?

Every project takes its own route. Trek runs on your Mac with a camp built in, so pack light and start walking.

Camp runs on macOS, Windows and Linux. iOS and Android apps are on the way.