Workspaces and Code Atlas
A workspace is the project folder used by a Syntheo task. Choosing the right workspace keeps file access, tools, history, and review in the right place.
Choose a workspace#
Use Add Workspace in the sidebar, then select one project folder.
Choose:
- a project root for normal work;
- a smaller package when it can be worked on independently;
- a larger shared root only when the task truly crosses several packages.
Always check the workspace shown near the composer before sending.
Organize workspaces#
You can:
- pin projects you use often;
- filter the sidebar;
- start a new thread from a workspace;
- archive an inactive workspace without deleting its project files;
- open workspace settings from its menu.
Read confirmation messages carefully before any delete action.
Use Code Atlas when discovery is hard#
Code Atlas helps Syntheo find related parts of a project when you do not already know the exact file.
It is most useful for:
- large or unfamiliar projects;
- tasks that cross several areas;
- tracing a feature or user flow;
- planning a broad change.
You can skip it for a tiny project or a known one-file edit.
Index a workspace#
- Open Settings → Workspace.
- Select the workspace.
- Find Code Intelligence.
- Choose Index codebase.
Use Sync index after a large branch change, rename, merge, or refactor. Clearing an index removes Syntheo's index data, not your project files.
Use @ when you already know the scope#
Code Atlas helps discover relevant areas. An @ mention tells Syntheo exactly what you want it to focus on.
Explain the sign-in flow, starting from @src/features/auth.Change only @src/components/EmptyState.tsx and its nearest test. Ask before
editing anything else.Use the task panels#
- Terminal: run or inspect project commands.
- Browser: reproduce and review web behavior.
- File Diff: inspect captured changes.
- Open: open the active project location in another app.
If a task uses a Virtual Edit or a room, these panels may point to its isolated location. Check the displayed location before editing externally.
Keep threads organized#
Use one thread for one coherent outcome. Give important threads clear titles, pin long-running work, and archive completed work when it no longer needs attention.
Next#
Learn how to keep and integrate work in Reviewing and applying changes.
← Prompts and context · Everyday work · Documentation use notice