# tackroom > Guides and reference for the tackroom CLI, in reading order. Philosophy says what tackroom is for; setup gets you running; the rest stand alone. ## Docs - [tackroom docs](https://yourconscience.github.io/tackroom/docs/README.md): Guides and reference for the tackroom CLI, in reading order. Philosophy says what tackroom is for; setup gets you running; the rest stand alone. - [Philosophy](https://yourconscience.github.io/tackroom/docs/philosophy.md): What tackroom believes about managing a coding-agent setup, and what it refuses to do. Each principle names something you can check. - [Setup](https://yourconscience.github.io/tackroom/docs/setup.md): tackroom setup sets up a machine in one step and asks nothing. It creates your config repo, imports what your harnesses already have, runs the first sync and installs the periodic sync job. You run it on each machine you use; this page also covers settings per harness, root instructions, upgrades and uninstalling. - [Commands](https://yourconscience.github.io/tackroom/docs/commands.md): Every tackroom command, grouped by task. Find what you want to do in the tables, each with a one-line description; flags, edge cases, exit codes, the config lookup order and output rules follow under Reference. tackroom help lists the commands and tackroom help --all adds every form and flag. - [Harnesses](https://yourconscience.github.io/tackroom/docs/harnesses.md): tackroom writes your setup into 16 coding agents, called harnesses, each in its own native format. This page is the capability matrix: what each harness gets today, the key that names it in tackroom.yaml, and where its files land. Look here before you rely on a surface in one harness. - [Skills](https://yourconscience.github.io/tackroom/docs/skills.md): A skill is a directory under ~/.agents/skills/ with a SKILL.md that has name and description frontmatter (agentskills.io convention). Skills you write sync everywhere; skills from other people's repos are treated as dependencies: pinned to a commit, audited and in cooldown until they are 72 hours old. This page covers writing, adding and publishing them. - [Roles](https://yourconscience.github.io/tackroom/docs/roles.md): A role is a Markdown file in ~/.agents/agents/ that tackroom renders into each harness's native agent format. Edit the canonical .md; sync regenerates the rendered files and every one carries a Generated by tackroom marker. - [MCP servers](https://yourconscience.github.io/tackroom/docs/mcp.md): Declare an MCP server once in tackroom.yaml and sync writes it into each harness's own config file. Stdio servers reach every harness; remote servers reach seven of them. - [Hooks](https://yourconscience.github.io/tackroom/docs/hooks.md): Declare a hook once in tackroom.yaml and sync registers it in every harness that has a hook surface, using that harness's event names. tackroom hook list shows what is registered natively, including entries tackroom did not write. - [Plugins](https://yourconscience.github.io/tackroom/docs/plugins.md): tackroom handles two kinds of plugin: Claude Code plugins, which keep their native layout and load in place from your config root, and agent-plugins-spec sources, whose skills and MCP servers sync like any other source's or reach Codex as a native plugin. Its own sync and jobs panel ships as a Claude Code plugin and a Pi package. Use this page to add either kind, or to get that panel. - [Memory](https://yourconscience.github.io/tackroom/docs/memory.md): tackroom runs no memory system. It captures nothing from sessions, indexes nothing and never writes a memory file. What it does is delivery: a file you list under instructions: goes into each harness's root instructions, so a memory file you keep reaches every session. - [Crons](https://yourconscience.github.io/tackroom/docs/crons.md): tackroom cron lists every scheduled job on your machines, runs and pauses launchd jobs, and installs jobs you declare as native units of the host's own scheduler. Use it to see what runs where and whether it ran, and to keep your own jobs in your config repo. tackroom runs no scheduler daemon of its own. - [Web view](https://yourconscience.github.io/tackroom/docs/view.md): tackroom view opens a local dashboard over your config: the sync state of every harness, outside sources with their pins, cooldowns and blocks, what is on disk, MCP and hook targeting, scheduled jobs and a YAML editor. It is where you look and act day to day; every action calls the same code as a CLI command, which stays the surface for scripts and SSH. - [Terminals](https://yourconscience.github.io/tackroom/docs/terminals.md): tackroom has integrations for tmux, zellij, Herdr, Tern and Rex, and a recipe for cmux. Each integration is optional and calls the same tackroom commands you can run in any shell. There are three kinds of integration: - [Comparison](https://yourconscience.github.io/tackroom/docs/comparison.md): tackroom is a user-level dotfiles manager for coding agents. It syncs skills, MCP servers, hooks, roles and root instructions across the harnesses you use, and pins and audits what you install from strangers. - [Troubleshooting](https://yourconscience.github.io/tackroom/docs/troubleshooting.md): Start with tackroom doctor, then tackroom status. This page lists the messages and states you are most likely to meet and what to do about each. - [Release notes](https://yourconscience.github.io/tackroom/docs/upgrading.md): What changed in each release since 2.0, newest first, with what to do on every machine that shares your config root, and how to move from dotagents. How to install a new release is in Upgrade.