Files, mentions, and context

Superconductor scopes prompts, files, diffs, and history to the active worktree.

Worktree context

Every terminal or chat session belongs to a worktree. That worktree provides:

• Commands run from the worktree directory.
• Diffs compare against the worktree base branch.
• Session history scopes to the task.
• Local API commands resolve the worktree from the CLI process’s current directory.

Copy context from another task into the prompt, link it, or handle it in a separate worktree.

File mentions

In native chat sessions, type @ to mention a file and point the agent at it. Examples:

Review @src/auth/session.ts and explain why the timeout test is flaky.

Update @src/content/docs/docs/cli-local-api.md to include the new worktree commands.

Edits to the prompt preserve mentions as explicit references.

Pasted and attached context

Paste text or attach files to supply material outside the repository, such as error logs, PR comments, product notes, or a reproduction transcript.

• The exact error and stack trace.
• The command that produced it.
• The relevant environment detail.
• The expected behavior.
• The recent change that might be related.

Shared parent context

In a shared-context workspace, shared context delivers notes that multiple related child repositories or worktrees need, such as:

• A short implementation plan.
• A spec or acceptance criteria.
• A cross-cutting constraint that each child worktree uses.

For multi-repository or multi-worktree parent and child workflows, see Shared context.

When the agent finishes, open the review view to inspect the resulting diff.