The recommended installation method is the installer on the download page. This guide covers installing from source if you already use Node.js and Git.
Commands use Bash on Linux, macOS, or WSL2. Replace values in <...> with your own information; do not run those placeholders literally.
#Get the source
Cockpit's repository is currently private. Source installation requires a GitHub access invitation. Once you have access:
mkdir -p "$HOME/Projetos"
cd "$HOME/Projetos"
git clone https://github.com/gruposaht89/cockpit.git cockpit
cd cockpit
If you already have a checkout, open the folder containing the root package.json. You do not need to use /DATA/Projetos.
#Install and build
npm run setup
This runs, in order:
npm ci
npm --prefix web ci
npm run build:all
There are two installations, at the root and in web/, each with its own lockfile. npm ci replaces the corresponding node_modules with the lockfile's dependencies. Do not use --omit=dev: building requires TypeScript and Vite. Output goes to dist/ and web/dist/.
#Included skills and activation
Installation runs postinstall and copies 160 bundled skills to ~/.cockpit/skills (or $COCKPIT_HOME/skills). Instructions, scripts, references, licenses, and pinned revisions from 25 sources are recorded in third_party/skills/manifest.json. Copying needs no additional Git or internet access. Reinstallation preserves existing files and activation choices. If npm scripts are disabled, first launch completes the copy; you can also run npm run setup:skills.
Under Settings → Skills → Add skill, import a SKILL.md, select a complete folder, paste a public GitHub link, or write instructions directly. Links can point to repositories, folders, or SKILL.md; choose a skill if several are found. A direct SKILL.md link imports only that file. Review the preview before adding it. Imports preserve existing skills with the same name and accept up to 8 MB total, 2 MB per file, and 256 files. They do not execute installation scripts.
Make this skill available to all agents is enabled by default and uses the shared catalog, including subsequent queries from agents already open. External tools and credentials require separate setup. Toggle individual skills in Settings or the Library.
Keep Make skills available to agents enabled in Settings → Skills or Library → Skills for automatic discovery. The master switch pauses the catalog without clearing individual choices. Preferences are stored in ~/.cockpit/skill-settings.json. Tasks receive suggestions based on role and request; the bridge exposes cockpit_skills for search and cockpit_skill for instructions and supporting files. DSH chat receives this context too. Explicitly selected member skills remain suggested while active. Mission roles, scope, and permissions take precedence.
The left-hand Skills menu offers search and an expandable list. Drag an active skill into an agent's conversation or click to add it to the focused agent. In DSH chat, it appears above the message and can be removed before sending. In a terminal, instructions are inserted for review before Enter. This never sends automatically or changes the member's permanent skills. Use click on mobile or with a keyboard. Disabled skills are unavailable here.
Deactivation applies to future queries and task deliveries, including existing MCP connections. It does not undo instructions already read or actions underway, or modify catalogs configured directly in CLIs.
External requirements are listed in the Library. NotebookLM needs its CLI and Google login; Strix, Agent Reach, Graphify, and RTK need their tools. RTK uses a Cockpit adapter preserving official documentation. GSAP and shadcn are installed in the project when needed. First use of Impeccable may download its executable.
The bundle includes Matt Pocock's code-review, to-spec, and to-tickets, and six official ai-memory skills for queries, pages, continuity, messaging, maintenance, and instruction installation. Matt Pocock's skills use the project's configured issue tracker. ai-memory requires a running server and its MCP connected to the agent; installation and connection guides accompany the skills.
Skills with external requirements offer Set up, including steps and official links. I've configured this skill's requirements is a saved manual confirmation, not a connection test or activation change. Settings groups guides by tool; shared requirements appear together, with tool summaries and individual skill briefings. The Library includes Portuguese summaries for all 160 bundled skills, which are searchable.
Context7 has one section, showing status and Manage key when a key is saved. Its official find-docs and context7-cli skills query documentation through the CLI without MCP. Anonymous usage is available; login or an API key raises limits. Save or remove the key in Settings → Skills. The server encrypts it, never returns it to the browser, and sets CONTEXT7_API_KEY for new native and DSH agents. Restart existing agents to apply changes. Saving does not verify authentication. Interactive CLI login remains under your control on the Cockpit server.
anti-ui-slop comes from UIZZE's official discovery index with a ZIP verified against the published SHA-256. The bundle covers 24 GitHub sources and that web source. To maintain it, edit third_party/skills/sources.json and run npm run bundle:skills, which fetches only recorded revisions and files. Maintenance needs Git, curl, and Python 3; installation needs only Node.js and the local bundle. These downloads happen during maintenance, not installation.
#Start and verify
For access only from your computer:
node bin/cockpit.js --host 127.0.0.1
Open http://localhost:4000. To also accept network connections:
npm start
Difference: npm start defaults to 0.0.0.0; the direct CLI defaults to 127.0.0.1 without a flag or environment override. Use the network IP shown in the terminal rather than assuming a fixed address.
In another terminal:
curl http://127.0.0.1:4000/api/health
The response includes ok and ptyBackend. Full terminals use python-pty or node-pty; pipe is a fallback without a TTY.
#Stop and recover
Press Ctrl+C in the server terminal. By default, the session host preserves agents for reconnection on the next start. Closing the dashboard does not automatically cancel work.
To stop agents when the server exits:
npm start -- --stop-agents
Worktrees are preserved. Reconnection depends on processes still existing; it does not survive a reboot or shutdown. Restored missions remain paused until you start or resume them.