Features
Projects
A project is a git repository that agents are allowed to work on. Each project is just three things: a name, an absolute path on your machine, and a base branch that variant branches are cut from and diffed against.
A workspace can hold any number of projects, and a single task can touch several of them. The repositories stay exactly where they are on disk; Modula references them in place.
Add a project
From the Projects page, click + New Project. There are two ways in:
- Existing: point Modula at a repository already on your machine. Pick the folder, and Modula detects its local branches so you can choose the base branch (typically
main). - Clone: give a git URL (HTTPS or SSH) and a destination folder, and Modula clones it for you.
Each project card shows its path, base branch, and any active worktrees, plus a warning if the path no longer exists on disk.
How agents use projects
When a Worker implements a variant, it creates a branch named feature/<task-slug>-v<n> from the project’s base branch and checks it out in an isolated worktree:
<project>/.worktrees/feature/mod-0001-fix-login-v1/If a variant spans multiple projects, the same branch name is used in each one, with one worktree per project. Your own checkout is never touched, and parallel variants never collide. Add .worktrees/ to each project’s .gitignore.
Diffs in the task view are computed against the base branch, and the Create PR button targets it.
In direct mode (a task with Worktree set to No), the Worker skips the branch and worktree and commits straight onto the base branch.
Guide your agents
Agents read each project’s CLAUDE.md (or equivalent agent instructions file) before touching code, so conventions you already maintain for coding agents carry over unchanged. Knowledge that agents discover about a project over time accumulates separately, in the workspace’s AI Wiki.
Remove a project
Deleting a project only removes it from Modula. The repository, its branches, and any worktrees on disk are left untouched.