Jupiter Workspaces

Jupiter turns every Jira issue into an isolated VS Code workspace.

Start a Jira task and Jupiter creates a dedicated git worktree, task branch, AI chat context, GitHub pull request, and Jira link in one flow. Work on multiple issues without switching one checkout back and forth or losing local state.

Why Jupiter?

Most Jira extensions help you view tasks. Jupiter helps you execute them.

• Work on multiple Jira issues in parallel with one git worktree per task.
• Preserve SSH or HTTPS remotes from your current workspace.
• Open a task-aware @jupiter chat context for the active issue.
• Push the branch, create a GitHub PR, and link it back to Jira.
• Diagnose Jira, Git, GitHub auth, and workspace remote setup from VS Code.

Flow

1. Run Jupiter: Setup Wizard.
2. Refresh Jira tasks in the Jupiter Activity Bar view.
3. Click Start Task on a Jira issue.
4. Jupiter creates a branch like feature/XYZ-12345-short-summary in a dedicated git worktree.
5. Use @jupiter /task in Chat for task context.
6. Create a GitHub PR from the task branch.
7. Jupiter links the PR back to Jira.

Screenshots

Requirements

• VS Code 1.120 or newer.
• Git available in PATH.
• Jira Cloud email and API token.
• GitHub sign-in in VS Code with repository access.
• A GitHub repository configured through Jupiter: Setup Wizard or detected from the current workspace origin remote.

Setup

1. Run Jupiter: Setup Wizard.
2. Follow the prompts for Jira URL, Jira credentials, GitHub repository, base branch, source repository, worktree root, and PR mode. Jupiter can auto-detect origin from the current workspace.
3. Open the Jupiter Activity Bar view and run refresh.
4. Start a task from the tree or with Jupiter: Start Task.
5. Use @jupiter /task in Chat to show the active task context.
6. Run Jupiter: Run Diagnostics if setup or authentication looks wrong.

Commands

• Jupiter: Setup Wizard: configure Jira, GitHub, git source, worktree root, and PR mode.
• Jupiter: Refresh Tasks: reload Jira tasks and group them by work state.
• Jupiter: Start Task: create a task branch and isolated git worktree.
• Jupiter: Open Worktree: open the task worktree in a new VS Code window.
• Jupiter: Open Task Chat: open or prepare @jupiter chat context for the active task.
• Jupiter: Create Pull Request: push the task branch, create a GitHub PR, and link it to Jira.
• Jupiter: Run Diagnostics: check Jira, Git, GitHub auth, settings, and workspace remote setup.

Settings

• jupiter.jira.baseUrl: Jira Cloud base URL.
• jupiter.jira.jql: JQL used to load task list.
• jupiter.jira.maxResults: Maximum Jira tasks to load across enhanced JQL search pages.
• jupiter.github.owner: GitHub owner or organization.
• jupiter.github.repo: GitHub repository name.
• jupiter.github.baseBranch: Base branch for worktrees and PRs.
• jupiter.github.draftPr: Create PRs as draft by default.
• jupiter.git.branchPrefix: Branch prefix, default feature.
• jupiter.git.remoteUrl: Optional SSH/HTTPS git remote URL used for source clones.
• jupiter.git.sourcePath: Optional local source repository used for worktrees.
• jupiter.git.worktreeRoot: Folder where task worktrees are created.
• jupiter.pr.titleTemplate: PR title template.
• jupiter.pr.bodyTemplate: PR body template.

Troubleshooting

Run Jupiter: Run Diagnostics first. It prints a structured report to the Jupiter output channel with the configured version, Jira URL, JQL limit, GitHub repository, git remote URL, base branch, source path, worktree root, Git availability, Jira credential check, GitHub sign-in state, and detected workspace origin.

If Jira tasks do not load, verify that jupiter.jira.baseUrl points to your Jira Cloud tenant and that the saved API token belongs to the same Atlassian account.

If worktree creation fails, verify local Git authentication for the configured remote URL. Jupiter preserves SSH remotes when it detects them, so your normal SSH key setup should continue to work.

Known Limitations

• Jupiter currently targets Jira Cloud and GitHub pull requests.
• Jira transitions, PR preflight, session cleanup, and multi-repository profiles are on the roadmap.
• @jupiter chat context is intentionally lightweight in the current release.