← Documentation
PLUXIX GUIDE
Workspaces
Keep local files, project context, Git state and task boundaries clear.
What a workspace contains
The selected local folder is the execution boundary for file reads, writes, Git operations, tests and project discovery. PLUXIX keeps the project on your machine while the account provides identity, routing and usage control.
- Repository files and local configuration.
- Git branches, status and diffs.
- Project intelligence such as symbols, dependencies and test signals.
- Conversation history and task evidence for the selected project.
Isolation
Use separate workspaces, branches or worktrees when tasks may conflict. A new chat is not a substitute for a separate Git working tree when two tasks can edit the same files.
- Check git status before starting and before handoff.
- Never delete a workspace with uncommitted changes unless you have a recoverable copy.
- Keep build artifacts and dependency caches out of the reviewable diff.
Workspace checklist
Before a meaningful task, confirm the project root, current branch, available package manager, test command and any local service the project needs. Ask the Agent to report this baseline before making changes.