Projects and repositories
A project is one piece of work and the repositories it touches. Add it once, and its terminals, issues and runs know where to go.
What a project is
A project has a name, its repositories and, when you add one, a plain folder that is not git. Terminals and the Files tile work in all of them; a run works only in a repository. The project's issues and notes belong to it, and each issue can name the repository it is about.
Add a project
- Press Add a project under your projects in the sidebar, or run Add a project from the command palette (
Ctrl+Shift+P). - Pick a folder in the dialog.
- A repository is added as it is, and the project opens.
- A folder that is not a repository itself but holds repositories side by side is shown first, with every repository directly inside it and a switch for each. Press Add the project: the project gets them all in one step, and the folder is where its terminals open.
Switch off any repository you do not want; Cancel adds nothing. With every switch off, the project starts with only its terminals until you add a repository. When a folder holds many, the list says that only the first ones found are shown.
Add or remove a repository
A project's Settings lists its repositories, each with its folder and its base branch, which you can edit. Add a repository picks another folder; the project's menu in the sidebar and the command palette have it too. Remove takes a repository out of the project, and its folder and everything in it stay.
A plain folder of the project says what it holds, and when it holds repositories, offers to add them in one press. When the project is a single plain folder with nothing git anywhere inside it, Set up git here makes it a repository, after a confirm that says exactly what it does. A repository with no commit yet offers Make the first commit the same way.
Where a terminal opens
In a project with several folders, a new terminal asks which one it opens in. A split opens where the pane it splits is, and a profile with a start folder of its own always opens there. A pane keeps its folder across a restart.
A project's views
The project in front lists its views in the sidebar. A project opens on the view you left it on.
- Terminals
- Its tab of panes. With none open, it offers what to open.
- Overview
- What needs a person first, then what is in flight.
- Runs
- Every run of the project on this machine, once the runner is set up. See Runs.
- Issues
- The Board, the List and the project's Routines. See Issues and notes.
- Notes
- The project's shared context for agents. See Notes.
- Settings
- Its name, its repositories, how its runs work on this machine, and Remove.
Other terminals
Other terminals is the tab for terminals that belong to no project. Each window has its own, and moving one into a window that has its own merges the two.
Rename and remove
Rename or remove a project in its Settings, or from its menu in the sidebar: right click its row, or press Shift+F10 on it. The name is a label: the folders on disk keep their own.
Removing takes the project out of Splitterm on this machine and closes its tab. Its folders, their branches and the run worktrees stay where they are, and adding it again brings the project back.
On Free
On Free, one project on each machine has issues, notes and the runner. Your other projects keep their terminals, Files and Git, and show their issues and notes read-only. Use it here instead, on one of them, moves the runner there. Pro lifts the limit.
Linked projectsPreview
On Pro, a project made in the dashboard can be attached to this machine from This machine, under Work from anywhere. It shows in the sidebar with a cloud mark. Its name, repositories and people are the dashboard's; on this machine you choose the folder each repository lives in.