---
title: "Projects and git worktrees in a Muse Code GUI"
url: https://helicon.sh/features/projects-and-worktrees
description: "Helicon groups every Muse Code thread under the directory the agent worked in, isolated git worktrees included, so parallel work across repositories has one place to live."
updated: 2026-09-19
site: Helicon
---

# Projects, grouped by working directory

Helicon's sidebar is organised by working directory. Every Muse Code thread appears under the project it ran in, and isolated git worktrees show up as their own entries with a badge, so running four agents across three repositories stays legible instead of becoming four terminal tabs.

## The unit is the directory

Muse Code sessions belong to a working directory. Helicon takes that seriously and makes the directory the organising object, so the sidebar is a map of where work is happening rather than a flat list of conversations.

## Worktrees are first class

An isolated git worktree is a different directory with the same repository behind it. That is exactly the setup people use to run several agents on one codebase without collisions, so Helicon lists each worktree as its own project with a badge showing what it is.

## Telling the state apart

- Running threads are marked while they run.
- Threads blocked on an approval are marked so you know which one needs you.
- Finished threads stay listed with their history rather than disappearing.

## Adding a project

Point Helicon at a directory and it starts a `muse serve` host for that workspace. Sessions already on disk for it, including ones from the terminal, are discovered rather than recreated.

## Frequently asked questions

### How many projects can I add?

As many as your machine can run hosts for. Each workspace gets one `muse serve` process, the same process the CLI would start.

### Do worktrees show as one project or several?

Several. Each worktree is its own directory and gets its own entry with a badge, because that is how the agent sees it.

### Can I run several agents at once?

Yes. That is the case the sidebar is built for, including seeing which of them is waiting on an approval.

## Related

- [Session history and resume](https://helicon.sh/features/session-history): Every Muse Code session, grouped by project, with full history and one click resume. Sessions started in the muse terminal TUI are discovered and resumable too.
- [Background work](https://helicon.sh/features/background-tasks): Send a running tool call to the background, stop one, or stop them all. Cancel a workflow run, or skip and retry its agents, without abandoning the thread.
- [Running agents in parallel](https://helicon.sh/use-cases/parallel-agents): Isolated worktrees, one sidebar, and clear marks for which thread is running, finished, or blocked on you. Plus the cost of all that parallelism, per thread.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt