Jarvis Agent Assistant

Give Copilot access to your work items, pipelines, and designs — without leaving VS Code.

Two ways to use it. Ask Copilot normally and it reaches your Azure DevOps, Jira, GitHub, and Figma through Jarvis instead of guessing. Or mention @jarvis for the full treatment: it reads the task, grounds a proposal in your open codebase, and shows you exactly what it would change. Either way, nothing changes until you say so.

Or just keep using Copilot

You don't have to type @jarvis at all. Jarvis plugs into normal Copilot Chat as a set of tools, so when your question needs something that isn't in your code, Copilot reaches through Jarvis to get it — instead of guessing from the files in front of it.

You, in normal Copilot Chat
  │   "why is the build red?"   "create a story for this"   "what's assigned to me?"
  ▼
GitHub Copilot ── realises the answer isn't in the workspace, calls a Jarvis tool
  ▼
Jarvis ── your identity, your sign-ins, nothing hosted in between
  │
  ├─► Azure DevOps — work items, pipelines, pull requests
  ├─► Jira — issues, status transitions, comments
  ├─► GitHub — issues and pull requests
  └─► Figma — frames, layers, and text from a design link
  ▼
Copilot answers with the real facts — and asks you to confirm before it changes anything

Ask "what am I working on?", "why did CI fail?", "create a user story for this bug", or paste a Figma link and say "build this screen". Copilot handles the conversation; Jarvis reaches your tools. Jarvis also hands Copilot ready-authenticated Azure DevOps and GitHub MCP servers, so agent mode gets those too — with no mcp.json to edit and nothing extra to install.

What it does

• Azure DevOps & Jira — reference a work item id (@jarvis 4011482) or a Jira issue (@jarvis PROJ-123) and get a codebase-grounded implementation proposal.
• Create and update work — ask Copilot to raise a task, user story, bug, or epic in Azure Boards or Jira, break work into sub-tasks, move something to Done, or comment on a ticket. Jarvis reads the project's own required fields first, so items land valid the first time — and it remembers any rejection so the next attempt already knows.
• Pipelines & CI — ask why a build is red and get the failed steps, log tails, and the commits in the run, not a guess from the YAML.
• Your day at a glance — a sidebar dashboard with a list per platform: Azure DevOps work items, Jira issues, Azure Repos pull requests, GitHub pull requests. Or ask @jarvis today for a briefing, @jarvis standup for ready-to-paste notes.
• Background mentions — comment @jarvis on your Azure DevOps work items or Jira issues and Jarvis notices, so you can pick up the task from VS Code.
• Figma context — paste a Figma link alongside a task to fold design details into the plan.
• One-click Accept — Jarvis applies the changes locally, creates a branch, commits, pushes, opens a pull request, and links it back to the work item.
• Learns from failures — when something goes wrong (a rejected push, a missing required field), Jarvis records the fix in your workspace and applies it next time instead of repeating the mistake.
• Stops Copilot re-reading your repo — instead of crawling the tree on every task, Copilot asks Jarvis for a repository map: structure, stack, entry points, where the tests live, and the files past work actually touched. One call replaces the whole "figure out where I am" step.
• Remembers solved tasks — when you open a pull request, Jarvis offers to remember the task: what it was, how you solved it, and which files you touched. Next time something similar comes up, Copilot is handed that summary and file list up front, so it reads a few known files instead of searching the whole repository. Off by default; you approve every save.

Why you'll like it

• You stay in control — proposals are inert previews. Accept, Decline, or refine in conversation. Decline changes nothing.
• Grounded in your code — proposals come from your actual open repository, not guesses.
• Uses your own Copilot — runs on your identity and your GitHub Copilot seat. No hosted services, no shared storage.
• It remembers, so it gets cheaper — solve a task, save it, and the next similar one starts from your solution and the files you edited instead of exploring the repository again. Opt-in, on-device, and nothing ever leaves your machine.

Getting started

1. Install the extension and reload VS Code.
2. Open the repository you want to work in.
3. Configure your task tracker:
   • Azure DevOps — you'll be prompted for your organization and project on first run.
   • Jira — run Jarvis: Configure Jira Integration and sign in.
4. In Copilot Chat, try it without @jarvis — Copilot will reach through Jarvis on its own:
   • "What am I working on?"
   • "Why did the last build fail?"
   • "Create a user story for adding a logout button."
5. Or address Jarvis directly when you want a full proposal you can Accept:
   • @jarvis today — your briefing for the day
   • @jarvis 4011482 — build a proposal from an Azure DevOps work item
   • @jarvis PROJ-123 — build a proposal from a Jira issue

Requirements

• VS Code 1.101 or later
• An active GitHub Copilot subscription
• An Azure DevOps and/or Jira account with tasks assigned to you

Privacy & security

Jarvis acts as you, using your own identity and Copilot seat. Nothing is hosted, shared, or stored outside your machine and the services you already use.

Nothing changes without your click. Reading is free — work items, issues, pipelines, designs. Every write is gated:

• Creating a work item, updating one, or opening a pull request from chat shows a confirmation naming exactly what will happen. Decline and nothing occurs.
• Branch, commit, push, PR, and the work-item link only run after you press Accept on a proposal — and they run deterministically. The AI model never drives git.
• Proposals themselves are inert previews until accepted.

The optional memory layer is local-only and redacts secrets before storing anything.

Full technical documentation, architecture, and configuration reference are available in the project repository.