SeeCodes Documentation

Everything you need to set up the workflow.

Welcome to the SeeCodes documentation. This guide covers installation, embedded video walkthroughs, connection, and day-to-day usage so your team can move from Jira planning to IDE execution without losing context.
Jira Cloud AppVS Code or CursorSetup guide + videos
View pricingAPI referenceSubmit an issue

On this page

7 sections

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.

Official marketplace listings

Developers install the SeeCodes extension from the new download page or the official marketplace listing for VS Code or Cursor.

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.

Video walkthroughs

Watch the executive overview first, then the Jira rollout walkthrough directly inside the documentation.

Use the right video for the right rollout moment

Start with the executive overview when leaders want a fast tour of the issue, project, dashboard, and settings surfaces SeeCodes adds after rollout. Then use the Jira setup walkthrough right below it when an admin is configuring fields, issue layouts, and board cards.

Executive overview

SeeCodes in Jira: Executive Visibility Into Engineering Delivery

A management-level tour of the Jira surfaces SeeCodes adds after rollout, including readiness badges, detailed issue progress, daily writeups, team competitions, dashboards, secure editor launch, and workspace settings.

Video walkthrough

SeeCodes in Jira: Executive Visibility Into Engineering Delivery

Click to load and play the privacy-enhanced YouTube embed for this guide.

What you'll learn

  • See how AI Readiness and AI Progress Report turn Jira issues into live, read-only progress signals instead of manual status updates.
  • Understand how the Daily Writeup page groups active work by assignee, highlights blockers, and prepares standup-ready updates.
  • Review how Team Competition surfaces solved tasks, active minutes, logic work, architecture work, UI or specification work, and relative effort for retrospectives.
  • Follow the secure Jira-to-editor handoff, manual progress submission, and automatic refresh flow that keeps Jira current with real implementation work.
  • Understand the broader management surface: cross-project analytics, visibility-aware reporting, backend region selection, launch-link expiration, and generated report language settings.

Best for

Watch this one first when you need a fast leadership and team-lead overview of what SeeCodes adds after rollout across issues, project pages, dashboards, and admin controls.

Explore the Jira App overviewPreview Daily writeupPreview Team competitions

Setup walkthrough

How to Setup SeeCodes in Jira

A Jira-admin-focused walkthrough showing how to add the SeeCodes fields, validate the Jira-to-editor sync, and expose AI Readiness directly on company-managed board cards.

Video walkthrough

How to Setup SeeCodes in Jira

Click to load and play the privacy-enhanced YouTube embed for this guide.

What you'll learn

  • Check whether the Jira project is company-managed or team-managed before editing layouts or board cards.
  • Add AI Readiness and AI Progress Report to the Task issue layout or screen so the issue surface shows live delivery state.
  • Place the fields where people will actually read them—commonly just below Description—and remember they are read-only by design.
  • Test the end-to-end flow by generating a SeeCodes Extension Task Link, opening the task in VS Code or Cursor, and submitting an AI Task Status Report from the editor.
  • If the project is company-managed, add AI Readiness to the board card layout so the badge is visible directly on Kanban cards.

Important Jira project-type note

Board card badge support is strongest in company-managed projects. Team-managed projects can still show AI Readiness and AI Progress Report on the issue layout, but board card badge options are more limited.

See board badge detailsOpen Jira App settingsInstall the extension

Installing the Jira Cloud App

The Jira side of the workflow starts in Atlassian Marketplace.
  1. 1Navigate to the Atlassian Marketplace.
  2. 2Search for SeeCodes Task Pulse.
  3. 3Click Get App and follow the prompts to install it into your Jira Cloud workspace.
  4. 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 extension in VS Code or Cursor

Developers install the companion extension from the official download page or directly from the correct marketplace listing for their editor.
  1. 1Open VS Code or Cursor.
  2. 2Open the SeeCodes download page or use one of the official marketplace listings below.
  3. 3Choose the Visual Studio Marketplace listing for VS Code or the Open VSX listing for Cursor.
  4. 4Click Install and reload the editor if prompted.

Official marketplace links

Any Install extension button on the site now opens the chooser on hover and the download page on click. You can also jump straight to the official listings below.

VS Code

Visual Studio Marketplace

Install the official SeeCodes extension from the Microsoft Visual Studio Marketplace.

Open official listing

Cursor

Open VSX / Cursor

Install the Cursor-compatible SeeCodes extension from the Open VSX marketplace.

Open official listing

Connecting Jira to VS Code

Once the app and extension are installed, SeeCodes can open a Jira task directly in the IDE.
  1. 1Open any active issue in Jira.
  2. 2Locate the SeeCodes panel on the issue view.
  3. 3Click Generate VS Code Task Link.
  4. 4When the secure link is created, click Open in VS Code or copy the one-time launcher URL.
  5. 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.