Influxx MCP Configs, Agent Skills, and Workspace Setup Hooks
Influxx workspaces get more capable when agents can load MCP servers and installable skill packs—and when every new worktree bootstraps itself with the same setup scripts. MCP Configs let you inspect and create workspace MCP server JSON for agents that consume MCP. Agent skills are installable instruction packs—Influxx CLI, Computer Use, Orchestration, Linear, emulator, per-workspace env, and more—installed through the Agent Skill setup UI. Setup hooks are per-repo scripts that run when a worktree is created so installs and env files are ready before the agent starts. This guide ties those surfaces to launch paths and the Getting started checklist item “Automate workspace setup.”
MCP Configs: Workspace Servers Agents Can Consume
MCP Configs are the cockpit surface for Model Context Protocol server JSON in a workspace. Use them to inspect what is already declared for the project and to create workspace MCP server JSON when agents you launch expect MCP. The goal is predictability: coding CLIs that read MCP—whether Claude Code, Codex, Cursor Agent, or another catalog entry—find a coherent workspace config instead of ad-hoc guesses. Influxx does not replace the agent’s MCP client; it helps you manage the workspace JSON those agents consume.
Treat MCP server definitions as capability you are granting to agent sessions on that checkout. Inspect before you trust, especially when servers can reach the network or local tools. Creating starter JSON is for agents that need a place to start; editing remains your responsibility as the repo owner. MCP fits the same isolation model as everything else in Influxx: worktree-scoped work, real files on disk, Local CLI sessions using your keys—not a hidden cloud rewrite of your tool list.
Inspect or create workspace MCP server JSON so agents that consume MCP share one coherent project config.
Work With MCP Configs
Open the project or repository setup surfaces that expose MCP Configs. Inspect existing workspace MCP server JSON for the agents you run. Create workspace MCP JSON when none exists and your chosen CLI expects MCP. Re-launch or refresh the agent after config changes so the session picks up the servers you declared. Keep MCP edits in the repo’s normal review flow when the team shares servers—agents on parallel worktrees should not surprise each other with divergent undocumented tools.
- Inspect: See workspace MCP server JSON agents will consume
- Create: Add starter workspace MCP JSON when the project lacks one
- Agent-owned clients: CLIs still load and honor MCP according to their own rules
- Worktree reality: Config lives with the project checkout isolation model
Agent Skills: Installable Instruction Packs
Agent skills are installable instruction packs that teach agents how to drive Influxx-specific and workflow-specific capabilities. Packs include Influxx CLI, Computer Use, Orchestration, Linear, emulator, per-workspace env, and similar skills exposed through the Agent Skill setup UI. Skills turn “the agent can open a terminal” into “the agent knows how to call Influxx orchestration, computer use, or task integrations the way this product expects.”
- Influxx CLI skill: Helps agents use the registered CLI surface for worktrees, terminals, and related commands
- Computer Use: Instruction pack for operating desktop apps and visible UI when workflows need real interaction
- Orchestration: Tasks, dispatch, inbox, decision gates, and coordinator-loop patterns for multi-agent control
- Linear: Skill support for Linear-oriented task workflows alongside task sources
- Emulator: Pack for mobile emulator control in workspaces that need device loops
- Per-workspace env: Patterns for environment setup tied to the active workspace
For development from source, skills may live under the repo skills/ tree. Day-to-day users should install through the app setup surfaces so discovery matches the active runtime and product UI. The Getting started checklist tracks enabling the Influxx CLI together with browser, computer, and orchestration skills—treat that checklist row as a ramp for skill-backed agent power, not only a binary install step.
Install Skills Through the App
Use the Agent Skill setup UI from the relevant setup or Settings surfaces (for example areas tied to orchestration or computer use). Install the packs you need—start with Influxx CLI if agents should script the cockpit, then add Orchestration for multi-agent control, Computer Use for desktop UI, Linear or emulator when those workflows matter. Confirm the Influxx CLI is registered when skills assume the launcher resolves on PATH. Re-open or relaunch agent sessions after install so new instruction packs are available to the CLI you run in the worktree.
Users install skills through the app setup surfaces; the repo skills/ tree is for development—not the primary end-user path.
Setup Hooks: Bootstrap Every New Worktree
Per-repo setup scripts and hooks run when a worktree is created. Use them to automate npm install, env file copies, local config generation, and other bootstrap steps so every feature branch starts ready for agents. Configure hooks under project or repository setup. The Getting started checklist item “Automate workspace setup” tracks whether you have engaged this path—open the checklist from the sidebar Setup guide entry or Settings → Onboarding checklist anytime.
Setup policy appears when you create a workspace: New Workspace lets you choose how setup runs for that worktree, and isolation options include running setup scripts on create with policies such as run, skip, or inherit. Parallel bake-offs benefit most—each competing worktree can install dependencies the same way instead of failing because node_modules or .env were never prepared. Hooks are automation you own; review them like any other repo script before they execute on every new checkout.
Configure Setup Hooks Once Per Repo
Open project/repository setup for the repo you care about. Define the setup scripts or hooks that should run on worktree create—dependency installs, env templates, and similar. Complete or revisit “Automate workspace setup” on the Getting started checklist so the cockpit reflects that the repo is automated. When you open New Workspace, pick the setup policy that matches the moment: run for full bootstrap, skip when you intentionally want a bare tree, inherit when policy should follow repo defaults. Confirm the first terminal or agent launch only after setup has finished if installs are heavy.
- When they run: On worktree create—before or as agents begin on that checkout
- What to automate: npm install, env files, and other per-repo bootstrap
- Where to configure: Project/repository setup surfaces
- Checklist signal: “Automate workspace setup” on Getting started / Setup guide
- Create-time policy: run, skip, or inherit when composing a new workspace
How MCP, Skills, and Hooks Fit Launch Paths
Launching an agent never required MCP or skills—but capable fleets usually do. New Workspace creates a worktree (hooks can run) and can start your chosen CLI. Tab strip and Quick Commands start agents on an existing tree. Sidebar note Run builds a context pack and opens a CLI tab. Tasks start from GitHub, Linear, or Jira items—Linear skills help when that provider is in play. The Influxx CLI can create worktrees with agents and prompts or add terminals with explicit commands; the Influxx CLI skill helps agents drive that surface. Automations schedule prompts on trees that should already be bootstrapped by hooks.
- Hooks first: Reliable installs/env before any CLI touches the tree
- MCP next: Workspace server JSON for agents that consume MCP tools
- Skills ongoing: Instruction packs for CLI, orchestration, computer use, Linear, emulator, env
- Then launch: Composer, note Run, tabs, Tasks, CLI, or Automations on a ready workspace
Playbook: New Repo Ready for Agents
Add the project in Influxx. Configure setup hooks for install and env bootstrap. Create workspace MCP JSON if your default agents consume MCP. Install Agent Skills you need—at minimum Influxx CLI when you want scripted cockpit control; add Orchestration and Computer Use when those workflows are in scope. Tick checklist items for CLI/skills and Automate workspace setup. Open New Workspace with setup policy run, pick Claude, Codex, Grok, or another catalog agent, and launch. Parallel worktrees then inherit the same bootstrap discipline.
Playbook: Orchestrated Multi-Agent Day
Ensure the Orchestration skill is installed and the Influxx CLI is registered. Create isolated worktrees (hooks run so each tree is healthy). Launch agents via New Workspace or CLI worktree create with prompts. Use orchestration patterns—tasks, dispatch, inbox, decision gates, coordinator loop—as exposed by the skill and product. MCP servers remain available to agents that read workspace JSON. Watch status and notifications; merge winners; delete the rest. Skills and hooks made the fleet possible; accounts and meters keep it sustainable.
Troubleshooting MCP, Skills, and Hooks
Agent cannot see expected tools: inspect MCP Configs and confirm workspace JSON exists and matches what that CLI reads; recreate or edit, then relaunch. Skill CTAs never finish: install through the Agent Skill setup UI (not only by copying a skills/ tree from development) and verify CLI registration when packs call Influxx. New worktree missing dependencies: confirm setup hooks are configured and that create-time policy was run—not skip. Checklist still shows Automate workspace setup incomplete: open repository setup, configure hooks, and refresh the Setup guide. Wrong runtime: install skills and register the CLI on the machine or distro where agents actually execute.
- Empty MCP: Create workspace MCP server JSON, then restart the agent session
- Missing skill behavior: Install via app setup UI; confirm Influxx CLI on PATH when required
- Bare worktree: Fix hooks and use setup policy run on the next create
- Checklist drift: Complete Automate workspace setup after hooks are real
Hooks bootstrap the tree, MCP declares tools, skills teach the agent—then every launch path starts from a ready workspace.
MCP Configs, Agent Skills, and setup hooks are how Influxx turns a raw git worktree into an agent-ready environment. Inspect or create MCP server JSON for CLIs that consume MCP. Install instruction packs—Influxx CLI, Computer Use, Orchestration, Linear, emulator, per-workspace env—through the app. Automate npm install and env files with per-repo hooks on worktree create, tracked by Automate workspace setup. Grounded in those product surfaces alone, you can launch from composer, notes, tabs, tasks, CLI, or automations knowing each new checkout and each skilled agent starts from the same playbook.
