AI is changing how fast we ship code. A feature that used to take days now lands in hours. But velocity without visibility is chaos — tickets pile up, MRs go stale overnight, and you start the next morning wondering "what did I even ship yesterday?"

Epic Lens gives you that visibility. It pulls your Jira epics, GitLab merge requests, and GitHub pull requests into a single VS Code sidebar so you can see everything at a glance: what's in progress, what's waiting for review, what's been approved, and what's stuck. When AI helps you move fast, Epic Lens helps you stay in control.

• Sidebar tree view — Epics with collapsible child issues, standalone issues listed below
• Merge request tracking — See all your open GitLab MRs and GitHub PRs with approval, pipeline, and conflict status
• Pipeline monitoring — Dedicated Pipelines view showing recent CI/CD pipelines on default branches, grouped by project, with expandable job details, cancel action, and configurable scope
• Provider cycling — Toggle between Both / GitLab / GitHub with a single toolbar button
• Dashboard — Board, List, and Settings tabs with status columns, progress bars, stats, and in-dashboard configuration
• Loading animations — Native VS Code notification toasts with spinners on all fetch/refresh commands; dashboard shows a blurred overlay spinner during load and refresh
• Live Jira data — Pulls real statuses, assignees, and priorities from the Jira REST API
• Scope filter — Show only your epics (mine) or everything in the project (all)
• Status/type filters — Filter by status category, issue type, or hide done issues
• Keyboard shortcuts — Chord-based shortcuts with Alt+E as the leader key
• Click to open — Click any issue, epic, or MR to open it directly in the browser
• Auto-refresh — Periodic re-fetch of epics and MRs on a configurable interval (default 5 min)
• Stale MR highlighting — MRs older than a configurable threshold show a ⏰ indicator with age
• Reviewer view — See MRs where you are assigned as reviewer; cycle between Authored / Reviewing / All scopes
• Status change notifications — Toast alerts when an MR/PR or pipeline status changes between fetches, with an "Open" button
• Jira-MR linking — Automatically links MRs to Jira issues by parsing issue keys from branch names (e.g. feat/DX-419-foo → DX-419). Linked issues show a 🔗 count; tooltips show MR details
• MR/PR dashboard section — The dashboard now includes a Merge Requests section below the Kanban board with status colors, stale flags, and reviewer tags

1. Install the extension
2. Open the command palette (Ctrl+Shift+P) and run Epic Lens: Configure Jira Credentials
3. Enter your Jira base URL, email, API token, and project key
4. Epics load automatically

A GitLab Personal Access Token with read_api scope is required.

1. Create a Personal Access Token with read_api scope
2. Run Epic Lens: Configure GitLab Credentials from the command palette (Ctrl+Shift+P)
3. Enter your GitLab host URL (defaults to https://gitlab.com)
4. Paste your token (stored securely in the OS keychain)

Alternatively, set the GITLAB_TOKEN environment variable or authenticate glab CLI with a PAT.

Note: If you used glab auth login with browser-based OAuth2 (the default), the stored token won't work. You need a Personal Access Token.

A GitHub Personal Access Token (classic or fine-grained) with repo scope is required.

1. Create a Personal Access Token with repo scope
2. Run Epic Lens: Configure GitHub Credentials from the command palette (Ctrl+Shift+P)
3. Paste your token (stored securely in the OS keychain)

Alternatively, set the GITHUB_TOKEN environment variable or authenticate with gh auth login (PAT-based).

The Merge Requests view has a toolbar button to cycle the provider filter:

Both → GitLab Only → GitHub Only → Both ...

Projects are prefixed with 🦊 (GitLab) or 🐙 (GitHub) when showing both providers.

A second toolbar button cycles the MR scope:

Authored → Reviewing → All → Authored ...

In Reviewing mode, only MRs where you are assigned as a reviewer are shown (marked with 📋). In All mode, both authored and reviewer MRs are shown.

The Pipelines view shows your recent CI/CD pipelines running on default branches (e.g. main), independent of any open MR. This is useful for monitoring post-merge pipelines.

• Fetches the 5 most recent pipelines per project that you triggered
• Queries your GitLab projects (by membership) and GitHub repos (by ownership)
• Pipelines are always grouped by project with provider icons; each pipeline description shows project name and time ago
• Pipelines are expandable to show individual job details with status and duration
• Provider cycling works the same as for MRs: Both → GitLab → GitHub
• Scope: configurable via epicLens.pipelineScope — Mine (only pipelines you triggered) or All (all pipelines on default branches). Also toggleable from the toolbar or the dashboard Settings tab
• Cancel pipeline — Right-click a running or pending pipeline and select "Cancel Pipeline" (with confirmation), or use the inline cancel action. Calls the GitLab/GitHub cancel APIs
• Canceled and successful pipelines are automatically filtered out of the tree
• Pipeline max age: only pipelines created within the last N days are fetched (default 7, configurable via epicLens.pipelineMaxAgeDays)
• Status change notifications fire when a pipeline transitions (e.g. running → failed)
• Included in auto-refresh alongside epics and MRs

The dashboard includes a third tab (Board / List / Settings) that lets you configure all Epic Lens settings directly from the webview UI — Jira connection, GitLab/GitHub hosts, and behavior settings. Click Save to apply changes.

1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API token
3. Copy the token and paste it when prompted by the configure command

Jira token is resolved in this order:

1. VS Code SecretStorage (OS keychain) — set via the configure command
2. ATLASSIAN_TOKEN environment variable — useful for CLI/CI environments

GitLab token is resolved in this order:

1. VS Code SecretStorage (OS keychain) — set via Configure GitLab Credentials
2. GITLAB_TOKEN environment variable
3. glab CLI config file (~/.config/glab-cli/config.yml) — PAT-based auth only, not OAuth2

GitHub token is resolved in this order:

1. VS Code SecretStorage (OS keychain) — set via Configure GitHub Credentials
2. GITHUB_TOKEN environment variable
3. gh CLI config file (~/.config/gh/hosts.yml)

All shortcuts use Alt+E as a chord prefix:

Jira statuses are mapped to these categories for filtering and display:

Each MR in the sidebar shows a status based on its current state:

MRs are grouped by project when you have open MRs across multiple repositories. Click any MR to open it in GitLab, or right-click for additional options.

# Install dependencies
npm install
npm install --prefix webview-ui

# Build
make build

# Watch mode
make watch

# Package .vsix
make package

# Release (auto-bump from conventional commits)
make release

# Install locally
make install

Epic Lens is part of the Andrevops developer tooling suite.

MIT