Task Relay
Plan your project, organize milestones and user stories, call an agent, and review the result in VS Code. Task Relay keeps your plans and work in workspace Markdown files and supports Codex, Claude, Devin, and human-owned work.
Major features
Feature execution choices: Select an agent, model and reasoning level per Spec Kit feature. Defaults show their source, unavailable choices retain recovery controls, and confirmed runs capture immutable execution history. Choices last for this extension session; authenticated provider compatibility remains unverified. See configuration and recovery.
Wide specification panel: Read and manage features in a full-height right-side Relay panel, half the content viewport at widths of 960px and above and full width below. Shared appearances, keyboard focus, saved-content refresh and reading position are preserved.
Verification commit picker: Select recorded feature commits, inspect exact Git changes, and explicitly confirm your actual verification results in the specification pop-out. Manual entry remains available with an explicit repository. Stale or unavailable evidence is explained; acceptance remains separate.
Spec Kit feature specifications: Enable the workspace Spec Kit workflow to create/select standard feature specs, share one root constitution, run installed agent skills, and track completed tasks from tasks.md. Relay shows feature IDs and titles instead of separate milestone/story/task items. Review, verification, and acceptance remain distinct. See setup and recovery.
Fast item and review pop-outs (0.4.12): Open task titles or review without rebuilding the board. Task titles show their existing preview while the captured details load. The file list loads independently, only the selected file gets a diff, and commit labels arrive separately. Switching files preserves the board and its scroll position.
Minimal background work (0.4.12): Typing causes no task scans. Startup and saved-file events keep a shared inventory current; external file events update affected paths. Recurring scheduling and the 30-second queue refresh remain enabled. Slow Relay UI startup retries share one render, preventing the loading screen from stalling.
Planning without workflow gates: Saved external edits reconcile automatically; lifecycle and session metadata do not block actions. Unsaved affected files are checked in the current VS Code window when an operation is requested. Competing saved inputs are retained for recovery. See behavior and enforcement inventory.
Direct Markdown authoring: New task files in JSON workspaces receive stable IDs automatically. Ordinary frontmatter and portable JSON synchronize in both directions, with local conflict recovery and dirty-editor protection. The planning CLI and proposal workflow are disabled. See direct authoring.
Commit-reference review: Store repository-qualified full SHAs in JSON; pop-outs derive immutable changes from Git while preserving legacy history and delivery context.
Milestone execution defaults: Open a milestone in Canvas or Planning Table and choose Configure execution defaults to edit work directory, agent, model, reasoning and run mode. Preview inherited values and affected tasks, clear overrides, then save through the existing JSON or YAML metadata writer.
Milestone JSON metadata: Track milestone status, execution defaults, branch and custom fields in Git alongside task metadata. New repositories and existing task-only JSON boards enable milestone storage automatically with backed-up migration.
Automatic JSON storage: New and existing boards enable JSON storage and two-way sync automatically, including previously dismissed migrations and older prose-only tasks. Original files are backed up, and unsaved edits remain protected. See JSON storage.
One public command: Open Relay UI. Manage tasks, settings, execution and review in the UI; obsolete palette commands, menus and shortcuts are retired.
Relay appearance: Choose Follow VS Code, GitHub Light, or GitHub Dark in Relay UI and Relay Manager. The workspace preference synchronizes panels without resetting edits or navigation; host high contrast takes precedence. Native Markdown and diff editors keep their editor theme.
Task commit history: Implementation, resume and correction prompts share a structured commit-recording contract with generated root AGENTS.md. Each task retains gitCommitReferences and compatible historical gitCommitEvidence for Relay pop-out review; custom prompts, tracked publication and direct-session bookkeeping follow the same rules.
Review workspace: Canvas and Planning Table open a wider review panel directly on Files, with searchable file navigation, inline Git diffs, Viewed progress and a recorded-commit selector. Overview, Verification and Task context keep long Markdown separate from code. Feedback and completion actions stay visible; Open native diff uses the same immutable comparison. Bounded caching reuses commit metadata, patches and blobs while revalidating canonical evidence and repository identity on each request. Results and native controls retain their committed-file tree.
Completed reviews update the board from the confirmed save without waiting for full workspace discovery; older in-flight scans cannot restore the previous status. Reviewed saves avoid redundant metadata reads.
Native review diffs open in a pinned tab in the editor group to the right, keeping the review workspace visible.
Faster review interactions: file switching reads only the selected task identity instead of rescanning the board. Completion validates identity and story closure in one fresh identity/relationship read, shows saving feedback immediately, and confirms persistence before the board refresh finishes.
Milestone Git branches: New tracked milestone items share the branch recorded in MILESTONE.md and a serialized checkout. Models commit their intended files with the work-item ID and publish verified per-item commit evidence. Missing branches use deterministic milestone names; legacy sessions retain their original resources.
Shared Relay UI layout: Canvas and Table use one project strip, summary and filter toolbar. Canvas fills the remaining workspace with independent filters, scroll and zoom, stable Fit, and bounded planning drawers.
Planning Table: Switch Relay UI between Canvas and a compact planning table. Keep project files above grouped milestone and nested story rows, inspect real planning documents, add Todo work, call agents, and review results through the shared native flows. Collapse groups, search, filter and sort without changing task files or agent selection order. Table navigation is retained separately from Canvas and legacy Relay Manager metadata columns.
Relay UI: Open a separate native VS Code planning tab with a top-down canvas of project, milestone, story and child-work cards. Work cards show an enlarged icon beside the type label, status at the top right, the clickable title underneath, and the Task ID below. Every item shows completed/total child-task counts from the full inventory, including 0 / 0 for items without children. Parent captions and child-collapse controls are removed; filters control visible work. Cards use heading-aligned milestone flags, compact status badges, separate planning-document and work-completion bars, and a stretching Review Changes button with a text-sized Call Agent button on the right. Review cards also show Mark Done between them, using guarded review acceptance. Click an item title to open a right-side rendered Markdown preview with Markdown editing and child-work creation controls. Work completion counts every story, task, bug and documentation item once using Done status, including hidden and nested work. Opening work or milestone details preserves the selected scope and filters. Filters stay visible inline without the header status shortcuts; the top-right toolbar includes Settings, Refresh and New Milestone icons plus the Appearance selector. Project file buttons show saved checkmarks and open individual review/build panels. Relay UI has no batch-modification controls. Milestone titles open a right-side rendered plan with saved context documents and Close/Open Milestone; Call agent offers explicit story refinement, drafting and next-ready-work choices. Inspect saved planning documents, draft Todo work, call an agent and review real results. Filter, focus, zoom or use the narrow-panel hierarchy; Relay Manager keeps its existing List, Table and Kanban views.
Plan first: Project plans, milestones and manual Todo stories need no agent setup or mandatory guidance files. Queue administration, provider settings and legacy drafting remain under Advanced.
Call Agent: Choose a scoped purpose from a project, milestone or story. Work milestone hands all items without completed implementation, including Todo and Request Changes, to one agent conversation; each result remains for review. Cancelled items and recurring schedules are excluded. Refine plans, draft stories, improve optional guidance or use a retained custom instruction in one conversation. Agents edit requested project files directly without a proposal service.
One story, then review: Start a Ready story or select the next Ready story by priority and path. Inspect results, accept ordinary work, approve tracked merges, or send corrections directly from the story.
Optional bounded continuation: Explicitly capture a maximum number of Ready stories in one milestone. Runs stay sequential, pause on uncertain outcomes and isolated integration boundaries, support Stop after current, and require Resume after restart.
Unified workspace: Keep project context, milestone scope, stories and attention together without top-level tabs. Milestone plans and progress use inline sections, while settings, queue administration, recovery and detailed Git actions live under Advanced. Existing views, drafts and native Markdown preferences remain supported.
Find and organize work: Filter by work type alongside status, owner, priority and milestone; inspect empty and closed milestones and unassigned work. Create and manage work from the same panel, reveal linked items outside the current filters, and keep explicit bulk selections and item-level outcomes visible.
Queue and recorded sessions: Inspect active, starting, waiting and failed requests, including repeated submissions for one item. Remove an exact waiting request, clear the captured waiting set, or explicitly release an active slot while leaving its process open. Resume the selected recorded conversation with its original provider and purpose; missing history offers recovery. Results links reuse review, saved-feedback retry and explicit acceptance controls. See execution and review semantics.
Guided merge recovery: Compare labeled target/story versions in VS Code's native diff editor, choose complete or edited content, preview the result, and let Task Relay commit the retained merge. Resolve managed Markdown and overlapping local edits in the same flow, retain displaced content, rerun checks, and separately approve the exact tested result. Destination changes require an explicit choice. See comparison choices and recovery.
Managed Markdown reconciliation: Approve & Merge preserves the reviewed file's LF or CRLF line endings when publishing guidance, preventing false changed-file errors between Windows worktrees and canonical editors. Actual intervening edits still stop publication.
Unified Approve & Merge: One guided flow selects the tracked story without requiring an open editor, handles its stopped session, reviews managed Markdown, commits explicitly selected implementation files, runs checks, and requests final merge approval. Interrupted preparation and recording resume through the same action; separate reconciliation or verification commands are unnecessary.
Approve & Merge session handling: If the story still has an agent session, approval asks to stop that exact session, waits for it to close, then continues required checks and final merge approval. If VS Code lost the terminal association, confirm that you stopped the named session directly in the approval flow. Cancelling preserves ownership.
Agent CLI status editing: Record any supported status by stable task ID through the shared writer, using current saved content without consequence confirmations. See CLI status editing.
Explorer filenames: Task Relay no longer adds task-status badges or colors beside files, including Ready, In Progress, Review, and work with active sessions.
Simple story approval: View Changes, choose Approve & Merge, and confirm once after the required checks pass. Request Changes reuses the story branch. Cleanup and diagnostics stay under Advanced Git actions.
Windows Git tracking: Long tracked filenames now check out in isolated worktrees, drive-letter casing preserves ownership, and partial setup errors show the original cause and the recovery command. Existing story branches are reused during recovery.
Isolated task execution: Each tracked task owns a taskID branch and worktree based on its milestone destination. Request Changes reuses that checkout, and a confirmed successful merge automatically cleans up the task resources while retaining commit history. Inspect partial setup and uncertain launches without duplicate execution. See configuration, permissions and recovery.
Verified local integration: Inspect committed story output and retained integration candidates, configure required checks, request same-branch corrections, and separately approve the exact tested commit for a local target. Acceptance, verification and merge remain distinct. Recover interrupted outcomes and preview/confirm safe resource cleanup. See verification, review and cleanup.
Unsaved target protection: Edit tasks and milestones, save planning output and call an agent from any recorded status. Saved changes, closed milestones, unfinished content, relationship or model diagnostics and existing work do not block explicit actions. Only unsaved changes in the target editor require save/revert.
Table cell editing: Opening a cell does not create an unsaved change. Click outside an unchanged cell to close it without a Save/Discard prompt. Dropdown selections and boolean checkboxes save immediately; navigation waits for an in-flight save without asking again. Free text, custom model/reasoning values and expanded YAML retain Save and Cancel. Execution dropdowns offer Use inherited value to clear an override. Failed saves retain input; Enter retries and Escape closes the editor.
One Request Changes window: Review different tasks and stories in one reusable GUI tab. Switch retained targets inside that tab; each keeps its own feedback, evidence and delivery state. Approve & Next and Skip / Next stay in the main UI without opening source tabs.
One tab per drafting interaction: Keep the brief, options, agent output and review in the same GUI tab. Switch stages inside the tab, reopen it in its existing editor group, and retain separate input for each stage. Different context/story interactions keep their own tabs. Explicit Open Draft/Open Source navigation remains available.
Table column layout: Drag a heading edge to resize, or focus its resize handle and use Left/Right (Home/End choose the bounds). In Columns, enter a width in pixels, use Move earlier/later, or check which properties to show. Item stays pinned and fits narrow panes; Item and Status remain visible. Layout is saved per workspace across scopes, filters and reopening, including preferences for temporarily absent custom keys. Reset column layout restores default widths, order and visibility while retaining selection, filters, collapsed groups and drafts.
Table: Choose List, Kanban or Table in Relay Manager. Use the Columns dropdown to check which properties are visible; Item and Status are always included. Choices are saved per workspace and retained across scopes and filters; hidden-column editors keep unsaved input available. Compare milestone-grouped peer rows with a pinned Item column, sticky headings and scrolling columns for scoped YAML properties. implementationCompletedDate, startDate, dependsOn and relatedTasks are hidden from Table; Item titles wrap fully within the pinned column, with icons aligned to the first line. Consistent theme typography, two-line property summaries and readable inheritance labels keep rows compact; full values remain available through tooltips and cell editors. Inline editors wrap their actions and keep focused controls visible at narrow widths and increased zoom. Milestones and Unassigned use rounded, spaced groups with subtly accented title-only headings spanning the table. Heading rows contain no property fields or static labels; peer items use regular table cells without tree guides. Named row groups, distinct selection colors and visible keyboard focus keep the hierarchy accessible. Separate collapse controls retain keyboard focus, headings remain visible during horizontal scrolling and full titles remain available on hover. Edit typed scalars or expanded YAML, use relationship/status/execution choices, and manage milestone defaults through milestone details. All eight recorded statuses use labeled icon badges; recognized priority, type and agent values use neutral chips. Compact inline dropdowns offer configured model and reasoning values, including model-specific reasoning choices; existing custom values remain available. Read-only explanations, inherited sources and stored Override labels distinguish cell behavior without pencil or lock icons. Typed/custom values remain safe text; focused, saving and error states retain accessible feedback. Status badges describe recorded metadata only. Keyboard save/cancel, retained drafts, compatible concurrent merges and independent Table state keep Markdown authoritative.
Passive automatic updates: Saved Markdown, queue/session activity and settings keep views current without background draft/workflow validation or repair prompts. Draft input and inactive-editor focus survive refresh. Recurring dispatch and real completion tracking continue; explicit operations check dirty target editors and report actual write or launch failures. See event boundaries.
Milestone closure: Close a milestone independently of its contained work, recurrence or queued sessions. Open/Closed remains visible metadata; closed milestones still support planning, editing and execution.
Recorded status controls: Choose any of the eight statuses for any managed work type from manager details, native Markdown properties, task commands, bulk changes or Kanban. Status edits preserve other content and create no approval, acceptance, feedback, schedule or execution. Confirm only concrete scheduling or queued-operation eligibility consequences. Compatible saved revisions refresh automatically; manual Review/Done leaves active silent work running. Queued intent and reviewed content have focused comparison/recovery. See status consequences.
Kanban: Switch between List and Kanban in Relay Manager. Status columns show stories, legacy children, tasks, bugs and documentation as peer cards. Use the stack-of-papers icon to show or hide milestone swimlanes. Click a plain milestone name to open its details, or use the left chevron to collapse its lane. Drag a card or focus its title and press Alt+M to edit recorded status freely, including in closed milestones. Status edits preserve all other content and leave approval, acceptance, sessions, queues and schedules untouched. Milestone moves preview children, detachment, configured file moves and relative-link rewrites. Filters, details, drafts, board scrolling and collapsed lanes are retained.
Shared milestone context: Below Relay Manager's filters, one button each opens an existing MILESTONE.md, AGENTS.md or SKILL.md, or opens generation setup for a missing file. The named milestone scope stays available when selecting its work and in either detail mode. Empty files open; unavailable files show diagnostics and Retry. Generation uses the retained GUI and exact-revision approval; closed milestones retain the same generation actions.
Finish drafting: Save & Close saves an exact reviewed draft and closes its GUI tab after confirmed success. Already-saved output offers Finish & Close. Failed, partial or changed-during-save input stays open and retained; closing does not approve Ready/Done or start another agent.
Clear drafting output: Agent Markdown appears automatically with waiting/review/saved guidance. Review-before-save uses Review Agent Draft and Save Reviewed Files; an already-saved draft shows Open Draft without another acceptance step. Manual import and advanced recovery are separate, current edits stay intact, and generated stories still require a separate Ready decision.
GUI output and feedback review: Copy prompts, paste and edit complete output, optionally preview before/after Markdown, then save directly. Feedback retains separate Save Feedback and Save & Send actions with actual saved-request delivery state.
Request Changes review tabs: Read complete ordered Results, repeated sections, fenced examples and review/acceptance history above the focused feedback fields. Inspect the captured revision, workflow blockers, session purpose and saved-request delivery; use eligible Approve & Next, Skip / Next, Return to Ready, human finish and recurring acceptance controls. Compatible snapshots refresh automatically; changed requirements/results or exact requests require focused review, preserving feedback; Next retains the prior draft. Palette commands offer separate Save Feedback, Save & Send, saved-request retry and Review Actions with CodeLens disabled. See reviewing feedback.
Retained drafting tabs: GUI drafts keep text and their captured target in memory across navigation and reopening. Save Draft for Later explicitly persists input; Reopen Saved Draft restores it after relaunch without submitting. Confirmed submission removes only its private saved copy after the last GUI tab closes; newer edits and failed/uncertain sends remain retained. Ctrl+Enter runs the GUI primary action and Ctrl+Alt+S saves the current visible fields. See the draft lifecycle.
Native editor actions: Open managed Markdown from Explorer, Quick Open, restored tabs, commands or Relay Manager to use above-line Status, Milestone, Type, Priority and Execution Settings actions by default. Native property/action pickers and complete Overview/Execution/Results views use shared recorded-status editing and explicit operational workflows; execution selections save directly to Markdown. Request Changes feedback uses a retained GUI editor. Keyboard commands remain available with CodeLens disabled. Optionally enable Use Native Detail Editor to open manager selections immediately to its right.
Native selection guide: Configure adjacent-right Markdown opening and tab reuse in the selection guide. Native actions remain available independently.
Relay UI pop-outs: Inspect work items and milestone plans in Canvas and Planning Table drawers. Item pop-outs show recorded commit history, changed files and inline Git diffs, with an action to open the same revisions in the native diff editor. The old detail pane, tabs and split layout are removed; List, Table and Kanban use the full width, and creation or retained edits open in a guarded pop-out.
Editor focus: Background Relay Manager updates preserve typing in native editors across List, Table and Kanban, with either Markdown selection preference. Keyboard focus and Table text selection still survive refreshes while working inside the manager.
Markdown editing: Enable taskRelay.openMarkdownToSide to open Markdown from Relay Manager in the editor group immediately to its right, keeping the manager visible. Reuse that group for focused, persistent file tabs, including task links and workspace or milestone guidance. This setting defaults to off, preserving normal editor-opening behavior.
Markdown content: Pop-out previews render saved Markdown, including tables, code and images, with source-editor actions.
Milestones and user stories: Organize work under milestones and stories, see progress and blockers, and keep shared context in MILESTONE.md, AGENTS.md, and SKILL.md. New and refined stories include an actionable ## Tasks checklist. Mark Ready records readiness; it does not add scope approval or acceptance history.
Configure Git Verification Checks: Run this Task Relay command to start an agent conversation that inspects the repository and configures its actual test/build commands in workspace settings. Existing guidance and unrelated settings are preserved; projects without real checks remain visibly unconfigured.
Draft, save, then review: Agents save requested draft files without a confirmation window. Review saved Markdown afterward and request revisions or explicitly submit implementation.
Direct story execution: Submit a Ready story to one agent session, track its checklist in the same file, then review verified results before accepting Done. Draft stories with existing User Story content offer Refine Story. Existing child-task stories retain their generation workflow until consolidated.
Agent and human work: Submit eligible tasks to Codex, Claude, or Devin through a sequential queue, or start human-owned work without an agent session. Configure inherited work directories, models, reasoning, and interactive or silent runs.
Explorer execution defaults: Right-click a managed milestone or nested folder and choose Configure Default Execution Settings to open its Defaults editor in Relay Manager. The task root asks for a milestone. Preview effective values and inheritance sources, save deliberate overrides to MILESTONE.md, or clear them to restore workspace fallbacks. Unsaved target editors require save/revert; saved changes use current content; missing MILESTONE.md opens generation setup.
Explorer managed work: Submit, resume, request changes, configure recurrence or accept work against the selected file. Recorded status does not gate explicit actions. Calls require a supported provider; Resume needs a real session; schedules and saved feedback need their operation inputs.
Explorer review approval: Right-click Review work for Approve beside Request Changes, or Approve & Merge for stories with Git tracking enabled through workspace, milestone or story settings. Approve records acceptance and marks Done; Approve & Merge runs the existing checks and final confirmation. Both target the clicked file, protect dirty target input and work with either detail setting.
Editor work actions: Draft, refine, submit, resume and manage a selected file, including inactive split editors. Saved revisions and status do not invalidate actions. Refinement preserves the supplied status. Dirty target editors require save/revert; unrelated editor changes do not.
Workflow and review: Organize work with any supported recorded status. Review recorded results, approve a specific revision, request changes, and keep feedback and acceptance history in the task file.
Editor review feedback: Request Changes targets the invoked source, including inactive editor groups, and opens the shared GUI regardless of the detail setting. Read protected results/history, compose structured feedback and save it without delivery, or deliberately Save & Send. Failed delivery retains the request for Send/Retry; multiline lists, headings and fenced examples remain intact in history.
Editor review approval: Review files offer Approve (check) beside Request Changes, or Approve & Merge (merge) for stories with Git tracking enabled through workspace, milestone, or story settings. Buttons target their own editor, including inactive split groups, and work with either detail setting or CodeLens disabled. Approve records acceptance and marks Done; Approve & Merge uses the existing checks and final confirmation. Dirty files and invalid tracking settings cannot be approved through these buttons.
Dependencies and relationships: Link related tasks, assign tasks to stories, and declare prerequisites with dependsOn. The board displays relationships and progress; their completion does not gate execution. Dispatch rechecks recorded status and effective provider/model settings.
Recurring tasks: Schedule daily, weekly, bi-weekly, or monthly work. Occurrences join the queue while the task remains recurring for future runs.
Get started
- Install the VSIX in VS Code and open a workspace folder.
- Run Task Relay: Open Relay UI from the Command Palette or use its button in Task Relay: Queue Manager in the Activity Bar.
- Create a project plan, then a milestone and user story. Write requirements, acceptance criteria and actionable tasks. Mark the story Ready when you want implementation to begin.
- Choose Call Agent and Start work, or use Work on next ready story from a milestone. Review results and choose Accept, Approve & Merge, or Request Changes. Optional bounded runs require a separate explicit choice. The default task directory is
devin-tasks; existing configured paths remain unchanged.
Tasks are Markdown files beneath the configured directory. A typical file looks like this:
---
status: todo
type: "task"
milestone: "release-1"
agent: "codex"
workDir: "."
---
# Add search filters
Describe the work and how to verify it here.
In JSON workspaces, Task Relay assigns a stable taskID when you create a task through the extension or save a new Markdown file in the configured directory. Supported types are task, bug, documentation, and user-story. Supported statuses are todo, ready, in-progress, review, re-work, done, cancelled, and recurring. Story sections and checklists guide the agent; they do not gate Ready or Submit. Mark Ready changes metadata without creating an approval fingerprint. Existing scope approval history remains intact. Select Submit Story from Ready to queue one implementation session; a successful launch moves it to In Progress. Check off work in the story file, record verification, and use Finish Work to reach Review. Explicit user approval records acceptance and marks Done through the review workflow. Every status control can record Done directly without creating acceptance evidence. A silent one-off agent records implementationCompletedDate after verified work; status alone never advances the queue. Recurring work keeps its existing completion timestamp contract.
Settings
The default task directory is devin-tasks. For example, add these workspace settings to .vscode/settings.json:
{
"taskRelay.directory": "devin-tasks",
"taskRelay.defaultAgent": "codex",
"taskRelay.modelOptions": { "codex": ["your-configured-model"] },
"taskRelay.defaultModels": { "codex": "your-configured-model" },
"taskRelay.recurringCheckInterval": "+5min"
}
For the full state and action rules, see the workflow state matrix. For release history, see CHANGELOG.md.
To keep Relay Manager visible when opening Markdown, enable Task Relay: Open Markdown To Side in VS Code Settings or set "taskRelay.openMarkdownToSide": true. It defaults to false; changes apply without restarting the extension.
Enable Task Relay: Use Native Detail Editor in VS Code Settings or add "taskRelay.useNativeDetailEditor": true to your settings JSON. This Boolean layout setting defaults to false; changes apply without restarting VS Code. With it absent or false, selecting work displays webview details. Enabling taskRelay.openMarkdownToSide alone does not change selection or hide those details.
With native detail enabled, mouse or keyboard selection opens the saved task, bug, documentation task, user story or canonical milestone MILESTONE.md immediately to the manager's right, reusing the adjacent editor group and persistent file tabs, or creating a right group when needed. The list uses the hidden detail pane's space. Native selection opens to the right with either split-preference value; enabling the setting also opens an existing selection. Mode changes retain selection, filters, native tabs and dirty buffers, protect webview drafts, and restore retained webview details when disabled. Native actions remain available independently of this layout setting or opening route. See native controls and workflow coverage, including selection, missing documents, retry and mode changes.
Development
npm install
npm test
npm run package:vsix
VSIX builds are written to artifacts/ in the repository root (for example, artifacts/task-relay-0.4.5.vsix).
Press F5 in VS Code to launch an Extension Development Host. Task Relay requires VS Code 1.90 or newer and is licensed under MIT.
| |