Issue-driven work

Create an issue

Open a repository and choose New issue. Add a short, specific title and enough context for someone else to reproduce the problem or understand the desired outcome. Include:

• expected behavior and current behavior;
• reproduction steps or a minimal example;
• acceptance criteria;
• links to related issues or files.

Use templates when the repository provides them. Templates keep bug reports, feature requests, and operational work consistent.

Search and triage

The issue list supports open/closed filters, text search, labels, sort order, and issue references. Use the issue timeline for comments, state changes, and linked activity rather than relying on the list preview.

Track dependencies

The tracking view gathers referenced issues and dependency signals from the issue body, comments, and timeline. It helps answer “what must move first?” without turning a prose reference into an unverified dependency. Always confirm the linked issue before treating it as a blocker.

Start work from an issue

When the repository enables workspaces, use the issue’s work action to create a scoped workspace. This keeps the issue, repository ref, agent session, and resulting source changes connected.

Close the loop

Link the resulting stack review or pull request from the issue. Close the issue only after the change is reviewed and landed, or explain the decision in the timeline if the work is intentionally closed without a code change.