Files, images, and context

Gyroscape starts with the active directory and discovers relevant files as it works. You do not need to paste an entire repository. Name a path, symbol, route, or feature when you know where the task belongs.

Repository instruction files can define build commands and conventions. Text inside an attachment or source file remains content; it does not replace your request.

Attach screenshots, images, logs, and supported documents from the composer. Explain what the attachment demonstrates and what must change. An image supplies evidence, not intent.

For screenshots, identify the incorrect area and desired behavior. Gyroscape can compare the reference with code and verify a rendered result when a local preview is available.

Gyroscape preserves real user messages and tool relationships needed for long tasks. Older history can be compacted while the objective, relevant results, and queued follow-ups remain available.

Restate a critical constraint before a risky final step when necessary, but do not duplicate every earlier message.

Do not paste passwords, private keys, recovery codes, or production secrets into a task. Prefer environment-variable names and redacted logs. Rotate any secret accidentally exposed in tool output.