Organize projects and sessions

Give each task a home#

A project specifies the working directory; a session records a task's conversation and tool activity.

Prepare a project#

Select the folder and check its path, branch, and existing changes. Keep related follow-ups together; create another session when the objective changes.

A new session does not copy the project or create an isolated Git checkout. Tasks sharing a directory can affect each other, so decide how to separate parallel edits first.

Start a scoped session#

1. Open a new conversation in the target project.
2. Name the outcome, evidence, and action boundaries.
3. Send the brief and check the reported directory and branch.

Investigate how member invitations handle expired links.
Confirm the current project and branch first.
Trace the UI and server code, citing file paths.
Do not edit files or start services.
Return the verified flow and unanswered questions.

Resume with the current state#

Open the session from the sidebar and read its latest result and pending actions. Request a recap for a long history, then recheck the branch, files, services, and account that may have changed.

Success means knowing the current objective, completed work, and next step. In split view, check the active conversation before acting; history does not guarantee that external state remains unchanged.

Resolve common mix-ups#

• Unexpected files: confirm the directory.
• Overlapping edits: inspect the diff and agree on ownership before changing anything.
• Missing context: supply the current outcome, files, and unresolved decision.
• Waiting: check approvals, questions, or service readiness.

Build a repeatable workflow#

Inspect work with files, terminal, and Review. Use memory and recap for handoffs and Goal Mode for sustained work.