Projects and Workspaces

A project in Deputy Shell is a sidebar entry with its own name that points to a dedicated workspace folder on your device. Projects keep separate codebases separate: each one has its own folder, and the sessions you start "in" a project are grouped under it in the sidebar.

Default Workspace

Deputy Shell always has a project called Default Workspace. It maps to a fixed folder and cannot be deleted — if you try, Deputy Shell keeps it and shows a message explaining that it can't be removed. It's the natural place to start if you don't need separate named projects yet.

Projects and sessions

Sessions belong to whichever project they were created in, and are grouped by project in the sidebar. A session's actual terminal location (its working directory) is normally the project's workspace folder, but the two can drift apart if a session is moved between projects — see Workspace Mismatch Warning.

Why exports are project-scoped

Workspace export always exports one project's workspace folder — not whatever folder a session's terminal happens to be sitting in at the time. This keeps export behavior predictable even if a session has drifted from its assigned project.

Workspace guidance for coding agents

Deputy Shell seeds a curated AGENTS.md into a workspace when the file is missing or still contains the retired one-line placeholder. The file explains Deputy Shell's Android/Bionic environment, workspace boundaries, available tools, credential safety, dependency rules, lifecycle constraints, and other guidance for coding agents. Existing non-placeholder AGENTS.md content is preserved, and the seeded file includes a section for project-specific instructions.