SeeCodes

SeeCodes connects the Jira task you are working on to the current VS Code workspace. It gives you a focused task workspace for research, implementation, diff review, local checkpoints, and Jira progress sync.

What you can do

• Connect this VS Code window to a Jira task from a Jira-generated link.
• Open task title, description, attachments, and task context inside VS Code.
• Draft a research plan before coding.
• Run implementation tasks with automatic, semi-automatic, or manual file selection.
• Ask AI to propose code changes, then review them by file or hunk before applying them.
• Review a diff or PR patch and get structured feedback.
• Compare local checkpoints, restore an earlier state, and compare the current workspace with the latest AI proposal.
• Generate an AI task status report and send task progress back to Jira.
• Add external context folders and generate a code graph when the task spans a larger codebase.

Main surfaces

Task Workspace

Use the task workspace to stay anchored to the Jira issue you are actively working on.

Research

Create or refine research notes tied to the current task.

Implementation

Prepare code changes, choose context, and inspect proposed diffs before accepting them.

Review

Paste a diff and get findings, risks, and suggested fixes.

Local History

Create lightweight local checkpoints, compare states, and recover quickly if an approach goes sideways.

Jira Sync

Send AI-generated task status updates back to Jira from VS Code.

Typical workflow

1. Open the Jira issue.
2. Use Generate VS Code Task Link in Jira.
3. Open the link in VS Code.
4. Review the task context in SeeCodes.
5. Work in Research, Implementation, or Review.
6. Apply accepted changes and sync status back to Jira.

Available commands

• SeeCodes: Connect Current Workspace to Jira Task
• SeeCodes: Disconnect Current Jira Task
• SeeCodes: Refresh Connected Task Context
• SeeCodes: Send AI Task Status Report to Jira

Notes

• The user-facing product name is SeeCodes.
• This extension is task-centered: each VS Code window is meant to stay attached to the Jira task it is actively working on.
• The details page and command list avoid internal or outdated naming and focus on real user actions.