Your first thread

This walkthrough takes one change from prompt to merge. It assumes you have installed Palisade and have at least one agent signed in.

1. Open a repository

Select Open Project on the welcome screen and choose your repository. A project is a repository opened in Palisade. It owns its threads, terminals, Preview, and .palisade/ settings.

2. Start a run from the Fleet board

The Fleet board is the home screen. Its composer starts new threads.

1. Choose a mode. Use spec to plan a change, or go to build it. See Spec and Go.
2. Choose an agent and a model for this thread.
3. Keep Isolated enabled for a separate worktree when building.
4. Write your prompt and select Start run.

The thread opens. Go tasks with isolation enabled get their own worktree. Spec mode writes planning documents under openspec/ in the project root. In the sidebar, the thread sits under Running.

3. Do something else

You can switch back to the Fleet board while the turn runs. Start more threads if you like. Keep isolation enabled for parallel Go tasks.

When the turn ends, the row moves to Unreviewed. If Palisade is in the background, you get a system notification. The dock badge counts threads that need you.

4. Jump to the finished thread

Press ⌘⇧U to open the next unreviewed thread. See Unreviewed turns.

5. Review and verify

Open the Review lane for the thread. Read the diff file by file and mark files as viewed. Select Run verify to run the project's named verify command.

6. Merge

Commit the thread’s changes, then select Merge. It runs any configured checks without current passing evidence and stops on failure. Select Open PR instead to use your normal pull request workflow; this requires the GitHub CLI (gh) installed and signed in.