CoincideFeature
A terminal in every thread
Run the dev server, the tests or a quick git command without leaving the conversation. Every thread has its own terminals, opened in the thread’s folder, and they keep running while you look at other threads.
Opening it
View › Show Terminal (⌘J) shows or hides the thread’s terminal; the first one starts on demand. Settings › General › Terminal places it in a Bottom panel below the chat, with its button in the rail on the left, or a Right panel beside the diff and browser preview, with its button among theirs at the top right.
A new terminal starts your login shell in the thread’s folder: its worktree, or the project folder, or the nearest folder that still exists if that one was moved. It gets your login shell’s environment, minus the variables describing whatever terminal Coincide itself was started from.
Tabs and panes
The slim header above the terminal has the thread’s tabs and a new-tab button on the left, and the working directory, split buttons and hide on the right. A tab can hold up to four shells, side by side or stacked. Shells keep running while their thread is off screen, until you close them, delete the thread or quit Coincide.
A program that reports progress the way brew and cargo do (the OSC 9;4 sequence) shows a progress bar on its tab.
Keys in a focused terminal
| Keys | Action |
|---|---|
| ⌘T or ⌘N | New terminal |
| ⌘D / ⇧⌘D | Split right / split down |
| ⌘W | Close terminal |
| ⌘K | Clear |
| ⇧⌘[ / ⇧⌘] | Previous / next terminal tab |
| ⌥⌘← / ⌥⌘→ | Previous / next pane |
| ⌘← / ⌘→ | Start / end of the line |
| ⌥← / ⌥→ | Move by word |
| ⌘↑ / ⌘↓ | Previous / next command |
| ⇧⌘L | Send the last command’s output to the agent |
While the terminal has focus it keeps these keys for itself, so ⌘K clears the terminal rather than opening the command palette, and ⌘W closes a shell instead of archiving the thread. The full list is in Keyboard shortcuts.
Handing output to the agent
Coincide’s shell integration marks prompts and commands, for zsh and bash, so it knows where the last command’s output starts and ends. ⇧⌘L attaches that output to the composer as a card, and selecting any text and pressing ⌘L adds the selection. Either way the agent gets exactly the error you’re looking at. The integration loads through its own startup files and never edits your dotfiles; if it can’t be set up, the shell starts as usual.
Project scripts
Commands a project runs often, such as its dev server or tests, can be saved as project scripts. Running one opens it in a terminal of the thread, and the one you ran last becomes the toolbar’s one-click script. A script marked “Run when a thread gets a new worktree” runs on its own in each new worktree, for setup such as installing dependencies.
Appearance
The terminal follows Coincide’s light or dark theme. Settings › General has GPU rendering (Metal; turn it off to draw with the CPU) and Translucent terminal, which lets the desktop show through, blurred. The terminal is built on SwiftTerm.
Things to know
- This terminal is yours. Agents run their own commands through their own tools, and those appear in the thread’s work log, not here.
- Terminals don’t run in the background agent host, so they stop when Coincide quits, even though agents keep going (see Background agents).