Influxx Git Providers, Linear, and Jira Task Sources
Influxx is strongest when work starts from a real issue, pull request, or ticket—not a blank prompt. This guide covers git providers (GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea), Linear and Jira task sources, how Integrations and Task Sources connect in Settings, how to browse PRs and issues in-app, how to open a worktree from a task, and how the Tasks page launches an agent workspace so hosted review and shipping stay in the same cockpit.
What This Guide Covers
You will learn where to review connected providers, why the GitHub CLI matters for in-app PRs and issues, how provider-aware Source Control labels remotes, how Linear API key and skill install entry points work, how Jira feeds “start workspace from issue” flows, how to link worktrees to host issues and PRs, and how the Setup guide’s Connect integrations step tracks progress. Everything here reflects shipped Integrations, Task Sources, Tasks, New Workspace, and Source Control surfaces.
Integrations are not a separate “git app” bolted onto chat. They feed the same multi-tab cockpit: left sidebar projects and notes, center tabs for agents and review, right activity bar for Source Control and Checks. Connect once, then start work from a task, write a short plan note if you need acceptance criteria in markdown, Run an agent in an isolated worktree, and open a PR or MR without bouncing to three browser windows.
Tickets and PRs should open workspaces—not scavenger hunts. Connect the host, pick the item, create the worktree, and keep review in the cockpit.
Where Integrations Live
Open Settings with ⌘, on macOS or Ctrl+, on Windows and Linux. Under General you will find Integrations for GitHub, GitLab, Linear, and other providers. Workflows also expose Task Sources so you can control which task providers appear in day-to-day pickers. Older docs may say Settings → Integrations → Review providers; search Settings for “integrations,” “GitHub,” “Linear,” or “tasks” if the rail labels have shifted—the panes remain the durable control surface.
- Integrations: Connect and review git hosts and task providers from Settings.
- Task Sources: Choose which providers surface when starting work from issues and tickets.
- Tasks page: Start a workspace from a GitHub, Linear, or Jira item with agent launch.
- New Workspace: Optionally link a GitHub, GitLab, or Linear task while creating a worktree (⌘N / Ctrl+N).
- Setup guide: “Connect integrations” tracks GitHub, Linear, or other task sources after onboarding.
Git Providers Influxx Knows
Settings → Integrations covers the git hosts Influxx is provider-aware for: GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea. You can browse pull requests and issues in-app, open a worktree from a task, and review without a full context switch to a separate web-only workflow. Source Control remains useful on local git alone, but hosted Create PR / MR composers and Checks shine once the remote host is connected.
GitHub is the deepest path today: the GitHub CLI (gh) is heavily used for in-app PRs and issues, and onboarding can optionally set up GitHub tasks by installing or wiring that CLI. GitLab is first-class for merge request creation alongside GitHub’s pull request composers. Bitbucket, Azure DevOps, and Gitea stay in the provider-aware set so branch labeling, remotes, and git operations match the host you use even when composer depth differs.
- GitHub: Issues and PRs in-app; gh CLI for PR/issue workflows; Create PR composers; issue/PR fields on worktree details; Actions-style checks surfaces.
- GitLab: Browse and open work from tasks; first-class Create MR path and merge-state awareness in hosted review chrome.
- Bitbucket, Azure DevOps, Gitea: Provider-aware git operations and labeling so the cockpit matches your remote even when hosted-review depth varies.
- Fork-aware compares: When push targets differ from the base repo, compare links qualify fork heads so review URLs stay correct.
Connect a Git Host and Start From a Task
Complete or revisit Connect integrations from the Setup guide (sidebar Setup guide entry or Settings → Get started / Onboarding checklist). In Integrations, connect the provider you use and finish any CLI setup GitHub needs for in-app PR flows. Open the Tasks surface or browse PRs and issues from the integration UI. Pick an item, open or create a worktree for it, and launch your agent—optionally with a sidebar plan note that captures acceptance criteria the ticket alone does not spell out.
Linear as a Task Source
Linear connects under Task Sources / Integrations as a first-class task provider. Setup supports an API key path plus skill install call-to-actions so agents that understand Linear workflows can install the matching instruction pack through the Agent Skill setup UI. Once connected, Linear items appear where Influxx starts workspaces from tracked work: the Tasks page, optional task links in New Workspace, and related pickers controlled by Task Sources settings.
Treat Linear like any other executable capability you hand to agents: connect with credentials you trust, install the Linear skill when you want agents to drive Linear-aware loops, and keep secrets out of committed notes. Skills install through app setup panels so discovery matches the active runtime (local, WSL, or remote host). After skill install, confirm the Influxx CLI is registered if the skill expects to call influxx from agent sessions.
Practical Linear Loop
Connect Linear in Integrations / Task Sources with your API key. Install the Linear skill from the skill setup CTA when offered. From Tasks, select a Linear issue and start a workspace. In New Workspace you can also link a Linear task and enable smart naming so the worktree card stays recognizable on the board. Write a short sidebar note if you need a local plan that expands the issue, then Run the note or let the Tasks launch path start the agent. Ship with Source Control and link host review fields as needed.
- API key: Required connection path for Linear as a task source.
- Skill install CTAs: Optional packs that teach agents Linear-oriented workflows.
- Tasks page: Start workspace from a Linear item with agent context.
- New Workspace link: Optionally attach Linear while creating the worktree.
- CLI surface: Product CLI groups include linear among discoverable command families for agent schemas.
Jira as a Task Source
Jira connects as a task source for “start workspace from issue” flows. Like Linear and GitHub items, Jira issues appear on the Tasks page so you can create a worktree and launch an agent without retyping the ticket into a blank terminal. Task Sources settings control whether Jira shows up in those pickers once connected through Integrations.
Jira’s product role in Influxx is deliberate and focused: feed real issues into workspace creation. It is not a replacement for your full Jira web UI. Use it to get an isolated checkout and agent session bound to the issue, then use Source Control, review notes, and hosted PR/MR composers on your git host to ship the change that closes the loop.
Start a Workspace From GitHub, Linear, or Jira
Open the Tasks page. Choose a GitHub, Linear, or Jira item that is ready for implementation. Start the workspace—Influxx creates worktree context from the task and can launch your chosen agent so title, description, and acceptance criteria ride along. Track board status (Todo · In progress · In review · Done), use notifications for long runs, and open Source Control when you are ready to commit, push, and create a PR or MR.
A ticket without a worktree is just a reminder. Start the workspace from the issue, then let Source Control finish the story on your git host.
Linking Worktrees to Issues and PRs
After a worktree exists, keep metadata honest. Open Edit Worktree Details from the worktree card menu or pencil control. Fill GitHub issue / GitHub PR fields (and related host links) so the workspace stays tied to the review it will produce. Optional sticky workspace comments are for short human intent on the card—not a substitute for the ticket or a sidebar plan. Smart naming in New Workspace helps the board and palette stay scannable when you run parallel experiments from similar tasks.
- Edit Worktree Details: GH issue / GH PR fields and related host links.
- Workspace comment: Sticky one-liner for humans browsing the board.
- Sidebar notes: Markdown plans under .influxx/notes when the ticket needs a local expansion.
- Create PR / MR: First-class for GitHub and GitLab from Source Control after push.
- Checks / PR Checks: CI status in-panel so you wait on green without leaving the cockpit.
How Integrations Fit the Shipping Loop
Connected providers make Source Control more than a local status list. After the agent works in the task-backed worktree, you annotate diffs with review notes, stage and commit, push, and open Create PR / Create MR. Provider-aware chrome matches GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea. First-class composers prioritize GitHub and GitLab. Checks and PR Checks fold host CI into the same operational loop; the embedded browser remains optional when you want the full host PR page inside the tab strip.
Recommended Integration Checklist
Connect at least one git host you actually push to. If you use GitHub PR flows in-app, finish gh CLI setup. Connect Linear and/or Jira if your team’s backlog lives there, and install the Linear skill when agents should speak Linear. Confirm Task Sources shows the providers you want. Tick Connect integrations on the Setup guide. Practice one full loop: Tasks → workspace → agent → Source Control → PR/MR → Checks. Add a second project only after the first remote path feels boringly reliable.
- Git host first: Remotes and Create PR/MR need a connected provider to shine.
- Task source second: Linear/Jira/GitHub issues feed New Workspace and Tasks.
- Skills where useful: Linear and related packs install via Agent Skill setup—not by guessing folders.
- Do not confuse surfaces: Integrations connect accounts; Tasks starts work; Source Control ships git.
- Remote parity: SSH/WSL projects still use the same Integrations model—confirm the active runtime before agent launch.
Multi-repo teams should register more than one project so Task-started workspaces can land in the right checkout. Folder workspaces with attached worktrees still benefit from task links and Source Control; provider awareness follows the remotes those worktrees track. Parallel agents each get their own worktree—start competing implementations from the same issue only when you intentionally want isolated experiments, then keep the winner and delete the rest.
Troubleshooting Integrations
If Tasks is empty, confirm the provider is connected and enabled under Task Sources, then refresh. If Create PR is disabled but visible, complete push or resolve the intent requirements shown on the control. If Checks are empty, confirm the branch is pushed, integrations are connected, and a PR is linked or discoverable. If GitHub PR actions fail, verify the GitHub CLI path used for in-app flows. If Linear skill commands fail inside an agent, confirm skill install status and that the Influxx CLI resolves on the machine where the agent runs.
When the Ticket and the Diff Disagree
Prefer the hosted issue as the source of truth for scope, and use a sidebar plan note when you need local acceptance criteria, constraints, or file-level guidance the ticket does not include. Run the note so the agent receives a context pack. Steer with review notes on the diff rather than rewriting the whole ticket in chat. After ship, merge on the git host and delete the workspace—Integrations got you into the work; cleanup keeps the board honest.
Integrations turn Influxx from a local agent launcher into a ticket-to-PR cockpit—connect the hosts you already use, start from the issue, and ship without leaving the window.
Related Influxx Help topics to explore by name: Getting Started with Influxx; Projects, Worktrees, and Isolated Workspaces; Source Control, Diffs, Pull Requests, and Checks; Running Coding Agents; Notes (local markdown and context); Settings, Keybindings, and Privacy; SSH Hosts, Remote Coding, Browser, and Design Mode. Together they close the loop from connected backlog to green checks.
Quick Reference
Keep this map nearby until Integrations muscle memory sticks.
- Settings → Integrations: Connect GitHub, GitLab, Linear, and other providers.
- Task Sources: Control which providers appear in task pickers.
- Git providers: GitHub, GitLab, Bitbucket, Azure DevOps, Gitea.
- Linear: API key + optional skill install CTAs.
- Jira: Task source for start-workspace-from-issue.
- Tasks page: Start workspace from GitHub / Linear / Jira.
- New Workspace: Optional GitHub / GitLab / Linear link + smart naming.
- Source Control: Commit, push, Create PR/MR, Checks after the agent works.
- Setup guide: Connect integrations tracks real connection progress.
When something still feels missing, remember Influxx separates account connections (this guide) from repository remotes on disk, from sidebar plans you choose to commit, and from agent CLIs you install yourself. Connect Integrations so Tasks and hosted review have somewhere to point; keep worktree isolation so parallel tickets never share a dirty tree; let Source Control publish the result to the host your team already reviews on.
