IDE & Browser Extensions

Bring Spedy into your editor and browser with the JetBrains plugin and Chrome extension.

Spedy offers extensions for JetBrains IDEs and Google Chrome so you can work with tickets and boards without leaving your tools.

JetBrains Plugin

The Spedy plugin for JetBrains IDEs brings your ticket system directly into the editor. Browse tickets, create new ones, write comments, jump between code references and tickets, launch AI coding agents pre-briefed with ticket context, and hand work off to runner teams — all without switching to the browser.

Install it from the JetBrains Marketplace.

Supported IDEs

IntelliJ IDEA, WebStorm, PyCharm, GoLand, PhpStorm, RubyMine, CLion, Rider, and Android Studio. Requires version 2025.2 or newer (Java 21+ ships with all modern JetBrains IDEs).

Installation

Open Settings → Plugins → Marketplace in your JetBrains IDE
Search for Spedy
Click Install and restart the IDE
Open the new Spedy tool window in the sidebar
Click Connect — your browser opens and you authenticate with your Spedy organization via OAuth

Features

Ticket Tool Window

A dedicated tool window in the sidebar shows your tickets. You can:

Filter by board, status, assignee, or search query
Open any ticket to see its full details (description, status, priority, assignee, comments)
Create new tickets directly from the IDE with Markdown support
Right-click any ticket row for quick actions: Assign team…, Launch in your AI agent, Copy ID + title + description, or Copy ticket ID

Live Ticket References

The plugin detects ticket IDs (like ACME-42, and multi-segment IDs like AH-1-157) in your code, comments, commit messages, and any other file the IDE can display. Detected IDs are highlighted and linked:

Hover over a ticket ID to see a docpop with the ticket's status (color-coded chip), title, assignee, priority, and due date
Click the ID to open the full ticket in the Spedy tool window

A bounded TTL cache keeps hover data fast even in files with hundreds of references, refreshing in the background and falling back to cached data when you're offline.

IntelliJ Tasks Integration

The plugin registers as a task repository for IntelliJ's built-in Tasks system. After you sign in, the active project is wired up automatically. That unlocks:

Branch naming — Open as Task on a ticket proposes a branch name derived from the ticket ID and title (e.g. AG-410/ai-launcher-from-ticket)
Status sync — finishing a task can transition the Spedy ticket to your team's "Done" status
VCS integration — issue navigation in commits and VCS tools opens the ticket detail directly in your IDE

Comments and Status Changes

Write ticket comments in a dedicated editor tab inside the IDE:

Full Markdown rendering
@-mention autocomplete for team members
Change ticket status directly from the comment editor

Launch AI Coding Agents from a Ticket

Open any ticket and click Launch in Claude Code (or right-click a row in the list and pick the same item). The plugin bundles everything the agent needs to start:

Fetches the ticket detail, every comment, and every attachment
Downloads attachments to .spedy/attachments/<ticket-id>/ so the agent can read them by absolute path
Composes a Markdown prompt under .spedy/prompts/<ticket-id>.md containing the title, status, assignee, full description, every comment (with author + timestamp), and the attachment file list
Opens a new terminal tab in the IDE and starts the agent with the prompt as its first message

The agent now knows what the ticket is about — no copy-paste, no context switching. You can choose your default agent in Settings → Spedy → AI launcher:

Claude Code — the recommended path; supports project-scoped MCP and Claude's permission modes
Codex CLI — the same prompt against the OpenAI Codex CLI
Junie — when the JetBrains AI plugin is installed, the prompt is copied to the clipboard and the Junie chat is brought to focus

CLI commands are configurable, so a custom binary path or wrapper script drops in cleanly. You can also toggle whether comments and attachments are included.

Zero-Config MCP Setup

Enable Auto-create .mcp.json on first launch in the AI launcher settings and paste an .mcp.json template. The first time you launch an agent in a project, the plugin writes a project-scoped .mcp.json from that template (validated before writing) so Claude Code — and any other MCP-aware client — can read and update Spedy tickets with no manual setup.

Existing .mcp.json files are never overwritten, and the toggle defaults to off so nothing is written to your project without an explicit opt-in.

Assign AI Runner Teams

Right-click a ticket and pick Assign team… to hand it off to a configured AI runner team — a pipeline of agents (planning, coding, review, respond) that picks up the job, comments on the ticket as it works, and moves it through your team's working/completion/failure statuses automatically.

Open the Runner tab in the same tool window to watch live SSE-streamed events — tool calls, model outputs, status transitions — and aggregated cost per job, without leaving the IDE.

Offline Code Review with `.spsx`

For reviews too small for a pull request, the plugin adds a .spsx selection-package format. Highlight a region in any editor, pick Spedy → Export selection as .spsx, and you get a single self-contained file bundling the selected code (with context), file path and commit/branch, the language for syntax highlighting, and an annotation thread.

Recipients open the .spsx like any other file: the plugin renders the annotated snippet with the original highlighting, shows the comment thread inline, and lets them add replies — all offline, with no server round-trip or Spedy account required. Save it back and send it on until the thread resolves.

Quick access to your assigned tickets from the browser toolbar
Create tickets from any web page
See ticket details in a popup without leaving the current page

Setup

Install the extension from the Chrome Web Store
Click the Spedy icon in the toolbar
Sign in with your Spedy account