Influxx Setup Checklist and First-Week Onboarding Plan
Influxx Setup Checklist and First Week — this guide turns the in-app Getting started / Setup guide into a practical first-week plan. You will walk every checklist item (multi-task worktrees, embedded browser, notifications, default agent, Influxx CLI and skills, integrations, workspace setup hooks, and multi-repo registration), learn how first launch seeds the cockpit, and structure days one through seven so notes, agents, source control, and parallel work become habits instead of one-time demos. Install guides cover the DMG; this article assumes the app opens and focuses on what to finish after onboarding.
First Launch Seeds the Week
On first open, Influxx walks you through essentials: pick a default agent (any CLI the catalog knows — Claude Code, Codex, Grok, Cursor Agent, OpenCode, and more), set theme and appearance, complete Windows-only shell and right-click steps when applicable, configure notifications so you know when an agent finishes or needs attention, optionally set up GitHub tasks via the GitHub CLI for in-app PRs and issues, and add your first project from the notifications step footer or later from the sidebar. Privacy is called out early: anonymous usage sharing is opt-in under Settings → Privacy (Telemetry). You can hard-disable with DO_NOT_TRACK, INFLUXX_TELEMETRY_DISABLED, or CI-oriented environment policy.
After that flow, the checklist is not a second wizard — it is a progress map against real product actions. Open it anytime from the sidebar Setup guide entry or Settings → Onboarding checklist (Get started). Every item is optional. Completing them teaches the surfaces you will use weekly: isolated worktrees, embedded browser, desktop alerts, default CLI, cockpit CLI plus skills, task integrations, per-repo bootstrap hooks, and more than one registered git project.
First launch makes Influxx yours; the Setup guide makes sure you actually use the cockpit — treat the checklist as week-one curriculum, not a gate.
How to Open and Read the Checklist
From the left sidebar, open Setup guide, or press ⌘, / Ctrl+, and open Get started / Onboarding checklist. Each row maps to a shipped capability. Items clear when the product detects real progress — for example a non-main worktree existing, notifications enabled, defaultTuiAgent set, CLI installed with related skills surfaces, integrations connected, setup hooks configured, or two or more git projects registered. If a row stays open, do the underlying action rather than hunting for a “mark complete” control.
Checklist Item Map (What Each Step Means)
Use this map as the spine of your first week. Complete items in an order that matches your work, not necessarily top to bottom — but do not skip notifications and default agent if you plan to Run notes overnight.
- Multi-task: Create at least one non-main worktree so parallel agents and feature isolation are unlocked
- Use Influxx's browser: Open a real page in the embedded browser (⌘⇧B / Ctrl+Shift+B is the common new-browser chord)
- Turn on notifications: Enable agent-complete notifications so finishes and needs-input events reach you
- Choose your default agent: Set defaultTuiAgent in Settings so Run and new agent tabs launch the CLI you intend
- Enable Influxx CLI: Install the CLI plus browser, computer, and orchestration skills surfaces the checklist expects
- Connect integrations: Wire GitHub, Linear, or other task sources for issue-driven workspaces
- Automate workspace setup: Add per-repo setup hooks/scripts so new worktrees bootstrap consistently
- Start work in multiple repos: Register two or more git projects when your week spans more than one repository
Day 1: Project, Plan Note, First Run
Add a project (existing folder, clone, nested multi-repo import, or SSH remote host path). Select the main worktree. Create a Sidebar note with goal, acceptance criteria, and constraints. Hover the note and click Run so Influxx builds a context pack and launches your default CLI agent in a worktree-scoped terminal. Open Source Control (⌘⇧G / Ctrl+Shift+G), skim the diff model, and optionally add a line note you could send later. Confirm theme/appearance from first launch still feels right for a long session. Tick mental boxes: project exists, note exists, agent launched once.
Day 2: Notifications and Default Agent Honesty
Revisit Settings → Notifications and the checklist’s Turn on notifications item. Enable agent-complete alerts (and sound choices where available) so a long Claude, Codex, or Grok run can finish while you are in another tab. Open Settings → Agents and confirm the default agent matches what Run just used. If note Run should always prefer a specific CLI, align Coding agents and Notes pane defaults now — day two is cheaper than discovering a wrong default on day five during a bakeoff. Privacy: confirm telemetry is still the opt-in choice you want.
Day two is also when Windows users should double-check default terminal shell, right-click behavior, and (if relevant) Windows vs WSL agent runtime so PATH matches where CLIs live. macOS users should notice Permissions under Privacy when computer-use skills will matter later in the week.
Day 3: Multi-Task — Your First Non-Main Worktree
Complete Multi-task by creating at least one feature worktree (⌘N / Ctrl+N New Workspace). Give it a clear prompt or reuse yesterday’s plan. Watch the workspace board statuses (Todo · In progress · In review · Done) so parallel work stays visible. This is the unlock for competing implementations: same prompt, second worktree, maybe a different agent. Delete or archive losers later; the checklist only needs you to create one non-main worktree to prove the muscle.
Day 4: Embedded Browser and Review Loop
Complete Use Influxx's browser by opening a real page in the embedded browser — docs, staging, or a PR page you care about. Keep coding and browsing in one cockpit instead of alt-tabbing. On the same day, practice the review loop: annotate a diff with review notes, Send notes to an agent, and commit from Source Control. Browser + review in one day teaches why Influxx is a cockpit rather than a terminal wrapper.
- Browser tab: New browser from the tab strip; checklist detects a real page open
- Review notes: Line comments on diffs; send unsent notes into a running agent
- Ship basics: Stage, commit (optional AI commit message), push, create PR/MR when integrations allow
- Checks: Glance at Checks / PR Checks so CI status stays in-cockpit
Day 5: Enable Influxx CLI and Skills
Open Settings → General / CLI and run Install CLI to register a launcher on PATH. Verify with influxx status (or influxx-ide / influxx-dev for your install flavor). Smoke-check influxx open --json, influxx status --json, and influxx agent-context --json. Complete the checklist’s Enable Influxx CLI item by also engaging browser, computer, and orchestration skills surfaces the product ties to that row — installable instruction packs via Agent Skill setup UI. You do not need to master every CLI subcommand on day five; you need the binary registered and skills available so agents and scripts can drive the cockpit.
Useful week-one CLI shapes include worktree list/create and terminal create with an explicit --command for a second agent on the active worktree. Prefer JSON flags when you script. Remember: coding agents (claude, codex, grok, …) are separate from the Influxx launcher binary name.
Day 6: Integrations and Automate Workspace Setup
Connect integrations — GitHub (gh CLI heavily used), GitLab, Linear, Jira, or other task sources — so you can start a workspace from a real issue. Complete Connect integrations on the checklist when at least one provider is wired for how your team tracks work. Then configure per-repo setup hooks under project/repository setup: install dependencies, copy env templates, generate local config. Run New Workspace once with setup policy run to prove the hook. Mark Automate workspace setup by actually engaging hooks, not by intending to. Hooks are how parallel worktrees stay cheap; Quick Commands remain for on-demand recipes.
Day 7: Multi-Repo and Week Retrospective
Complete Start work in multiple repos by registering a second git project you truly touch this week — not a throwaway folder. Switch between projects in the sidebar and confirm notes, worktrees, and Source Control attach to the active workspace. Retrospective questions: Did notifications fire when agents finished? Did the default agent stay correct? Did a non-main worktree save you from dirty-tree collisions? Did the browser tab replace an external window at least once? Did hooks save a manual install? Capture answers as a floating note or a Sidebar note titled “Influxx week one” so next week starts from written truth.
A finished checklist means the cockpit is wired; a finished first week means you shipped through notes, agents, and review without leaving the window.
Suggested Order When Time Is Tight
If you only have two focused hours after install: (1) default agent + notifications, (2) project + plan note + Run, (3) one non-main worktree, (4) Source Control glance. Push CLI, integrations, hooks, browser, and second repo into the next sessions — but keep the Setup guide open so unfinished rows stay visible. The checklist is a progress map, not a certificate: skipping Automate workspace setup is fine until the second parallel worktree makes bootstrap pain obvious.
- Must for overnight agents: Notifications + correct default agent
- Must for parallel work: Multi-task non-main worktree
- Must for issue-driven teams: Integrations
- Must for monorepo pain: Setup hooks
- Must for scripted fleets: Influxx CLI + skills
- Must for multi-product weeks: Second git project registered
First-Week Habits Beyond the Checklist
Write plans as Sidebar notes before you chat at an agent. Prefer New Workspace for competing approaches. Send review notes instead of pasting vague feedback into a prompt. Decide early whether .influxx/notes are committed as shared plans or gitignored as personal scratch. Remap only the shortcuts that hurt (Settings → Shortcuts); learn Mod+N, Mod+Shift+G, Mod+J, and Mod+, first. Pair mobile companion later in the week if you want phone-side notifications when agents finish — Settings → Mobile — after desktop notifications already work.
Appearance and Quick Commands deserve a deliberate pass once the checklist is mid-flight: theme and zoom for long sessions, then a handful of global or per-project Quick Commands for test and lint lines you still copy from READMEs. Those topics have their own deep help articles; week one only needs “comfortable chrome” and “two recipes you actually invoke.”
Troubleshooting Checklist Friction
If Multi-task will not clear, confirm you created a feature worktree rather than only renaming the main checkout. If the browser item stays open, open a real URL in an Influxx browser tab, not only an external browser. If notifications never arrive, re-enable agent-complete alerts and verify OS notification permission for Influxx. If default agent looks wrong on Run, set Coding agents and Notes defaults explicitly. If Enable Influxx CLI stays incomplete, finish Install CLI and the related skills installs, then re-open the checklist. If integrations do not count, complete provider review/connect under Settings → Integrations / Task Sources. If hooks do not count, save a real setup script on the repo and create a worktree that would run it. If multi-repo will not clear, add a second distinct git project from Add project.
What “Done” Means for Week One
Week one is complete when: first-launch defaults (agent, appearance, notifications, privacy choice) are intentional; at least one project and worktree are active; you have Run a plan note successfully; Source Control review is familiar; the Setup guide shows honest progress on multi-task, browser, notifications, default agent, and whichever of CLI, integrations, hooks, and multi-repo match your real job; and you have a short written retrospective. You do not need every catalog CLI installed or every Advanced/Labs toggle explored. You need a cockpit that can take a plan to an agent to a review without improvising the wiring each morning.
- Onboarded: Default agent, theme, notifications; telemetry opt-in reviewed
- Plan → Run: Sidebar note launched a real CLI agent once
- Parallel ready: Non-main worktree created (Multi-task)
- Browser touched: Embedded browser opened a real page
- Wiring matched to role: CLI, integrations, hooks, multi-repo as needed
- Retrospective captured: Note what to automate next week
Install gets you a window; the checklist gets you a cockpit; the first week gets you a habit — plan, run, review, parallelize, repeat.
Quick recap: complete first launch, then open Setup guide / Settings → Onboarding checklist. Work the eight progress items — multi-task, browser, notifications, default agent, Influxx CLI and skills, integrations, automate workspace setup, multi-repo — across a seven-day rhythm that also practices note Run and Source Control. Keep privacy opt-in honest. Use related Influxx help for appearance and Quick Commands, the full CLI catalog (Claude, Codex, Grok, and peers), worktrees, SSH hosts, and agents/parallel runs when week two demands depth. The checklist tracks real progress; your first week proves the cockpit is how you ship.
