Projects, workspaces, and tasks

A project points to a directory on your machine. File tools, terminal commands, language services, change tracking, and Git status resolve from that directory.

Moving or deleting the folder outside Gyroscape can break the project link. Add it again if its path changes. Adding a project does not silently copy the whole repository into a hosted editor.

Create a new task when the objective, branch, or acceptance criteria change materially. Reuse a task for follow-up work on the same outcome so its decisions and tool results stay connected.

Use a result-oriented title such as “Keep desktop sessions signed in” instead of “Fix bug.” Titles are searchable in the sidebar.

When workspace isolation is enabled for a Git project, Gyroscape can use separate working directories so independent tasks do not edit the same checkout. Each workspace keeps its own path and source-control state.

Wait until a workspace is ready and check the active workspace before commands, review, or launching a development server.

Gyroscape can inspect Git state, show diffs, and run requested source-control commands. You remain responsible for the branch, commit, push, and release destination. Review before committing and verify the remote before pushing.

Existing uncommitted work belongs to you. Mention it when it overlaps the task so unrelated edits are preserved.