Getting started
SeeCodes is designed to bridge the gap between Jira planning and VS Code execution.
Jira Cloud admin access
Setup starts inside Jira Cloud and requires administrator permissions for the workspace.
VS Code or Cursor
Developers need VS Code or Cursor installed on their local machine.
SeeCodes Task Pulse
Both the Jira listing and IDE extension are published as SeeCodes Task Pulse by eprojac.
Before you install
The normal Jira App path is Forge-managed. Admins choose the supported SeeCodes route, the one-time launch-link lifetime (1–14 days), and the report language in Jira settings instead of distributing raw backend keys.
Installing the Jira Cloud App
The Jira side of the workflow starts in Atlassian Marketplace.
- 1Navigate to the Atlassian Marketplace.
- 2Search for SeeCodes Task Pulse.
- 3Click Get App and follow the prompts to install it into your Jira Cloud workspace.
- 4After installation, open Apps > SeeCodes Settings to choose the supported SeeCodes route (root, /eu, or /uk), set the launch-link lifetime (1–14 days), and choose the language used for task status and daily writeups.
Installing the VS Code Extension
Developers install the companion extension directly from the editor.
- 1Open VS Code or Cursor.
- 2Navigate to the Extensions view (`Ctrl+Shift+X` or `Cmd+Shift+X`).
- 3Search for SeeCodes Task Pulse published by eprojac.
- 4Click Install.
Connecting Jira to VS Code
Once the app and extension are installed, SeeCodes can open a Jira task directly in the IDE.
- 1Open any active issue in Jira.
- 2Locate the SeeCodes panel on the issue view.
- 3Click Generate VS Code Task Link.
- 4When the secure link is created, click Open in VS Code or copy the one-time launcher URL.
- 5Your IDE opens, exchanges the one-time launch code for the real task permit, and then pulls the stored task context automatically.
What the secure launch link actually does
Under the hood, the Jira App first bootstraps a single-use Jira backend request key, then calls
/v1/security/vscode-link. The server accepts each Jira request key only once, keeps it short-lived, binds it to the same tenant/session context, and atomically rotates the next key after a successful call. The browser-facing launcher carries only a one-time code. After VS Code or Cursor opens, the extension exchanges that code through /v1/security/launch-exchange, and the server rejects the exchange unless the code is unused and the supplied projectId and taskId exactly match the bound task before hydrating from /v1/tasks/context.Using the AI Implementation Assistant
Once connected, the SeeCodes sidebar in your IDE displays the task details and lets the developer control the execution flow.
Context tab
Use the Context tab to select which files the AI should analyze.
Implementation tab
Use the Implementation tab to instruct the AI on what changes to make.
Diff review
Review proposed diffs and accept or reject hunks before applying them to your workspace.
What syncs back to Jira
Task execution uses permit-scoped routes such as
/v1/tasks/init, /v1/tasks/{runId}/start, and /v1/tasks/{runId}. Jira-visible state is written back through /v1/tasks/{taskId}/progress and /v1/tasks/activity-snapshot, so issue fields, daily writeups, and team competitions all read from the same structured backend state.Understanding the Jira Dashboard
Managers and Scrum Masters can access the SeeCodes Dashboard through Jira global navigation.
- Track total tasks and active users across the team.
- Review a timeline of progress for AI-assisted tickets.
- Keep planning, execution, and standup reporting aligned without micromanagement.
What the dashboard is for
The dashboard gives leadership visibility into AI-assisted work while keeping the underlying workflow anchored to real task and code activity.