Projects & local terminals
Create a project
Select + Project, enter a name and choose a directory. A project groups sessions; its directory can be added later, with the default working directory used in the meantime.
Use the + beside a project to create a session in it. New session can also create a standalone terminal without a project.
Choose a shell
Select detected PowerShell or Git Bash, or supply a custom executable. Enter one argument per line instead of placing a whole quoted command in the executable field.
| Field | Example |
|---|---|
| Name | Build and test |
| Working directory | D:\Work\website |
| Executable | C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe |
| Arguments, one per line | -NoProfile |
Verify the directory before starting. The default PowerShell preset uses -NoProfile. Missing shells are not installed automatically. Start tools such as Codex manually inside the terminal.
Switch, configure and revisit output
Switch with the top tabs or sidebar. Sessions can be pinned or renamed. Program-provided titles do not overwrite saved names.
Properties changes font size, shell and arguments. Shell changes apply to the next launch; the current process keeps its original settings. Reopening a closed session starts a new process.
An output snapshot is retained text, not process restoration or a complete TUI recording. Local snapshots are capped at 2 MiB per session. Removing a session record or project removes related snapshots; removing a project does not delete its directory on disk.
Search projects, recents and files
- Projects search matches project names.
- Recents search matches recent session names and program titles.
- Files search matches filenames and relative paths inside the current project, not file contents.
Search supports Chinese, case-insensitive matching, space-separated keywords, arrow-key navigation, Enter and Escape.
Next: Files · Environment & proxy