Overview
A Project binds a Host and working directory to private Actions and Snippets. Opening it restores the operational context of a repository without repeatedly navigating directories or reconstructing the commands used there.
Project Actions are copied into the Project and can be customized independently from public launcher Actions. This lets two repositories use different flags, package managers, test targets, or agent prompts even when they live on the same Host.
When to use it
- Return frequently to a repository, monorepo package, service directory, or infrastructure workspace.
- Keep repository-specific agent launch, test, build, preview, release, and deployment commands beside the working directory.
- Maintain Project-only Snippets for branch checks, package filters, log paths, or prompts that make sense only in that codebase.
- Separate several repositories on one Mac or server so terminals and Actions always start from an explicit path.
- Create stable mobile entry points for development, staging operations, documentation work, or incident response.
Return to one repository every day
Bind the Host and exact working directory once. Opening the Project starts terminals, agents, and Actions in that directory, avoiding accidental work in a parent folder or another checkout.
Separate monorepo packages
Create Projects for the frontend, API, mobile app, or infrastructure package, each with its own test filters, dev server, build commands, and prompt Snippets.
Keep operational context visible
For staging support or incident response, group the service directory, log commands, health checks, restart Actions, and diagnostic prompts into one named workspace.
How it works
- Choose a Host and set the project working directory.
- Add the Actions and Snippets used by that repository.
- Open the Project whenever you need a terminal, agent, or repeatable task in that context.
Practical guidance
Create one Project per repository or service. A precise working directory makes every terminal and Action safer because the execution context is visible before you start.