Getting started
From nothing to a team, your assistants connected, and your board open in a browser. It takes one command and a couple of answers.
Install
Run this in a terminal on each machine you code on:
curl -fsSL https://metiche.xyz/install.sh | sh
The script is served as plain text at that address, so you can read it before you run it. It is POSIX sh and never uses sudo. To see every change and every call it would make without doing any of them, run it with --dry-run.
Create a team, or join one
The installer asks which of two things you are doing:
- join, when a teammate sent you a join code. You paste the code at the prompt, and it is not echoed.
- create, when nobody has set the team up yet. You type a team name.
Creating a team prints its first join code once, in a box. Anyone holding that code can join the team and see its board, and that first code has no use limit and no expiry. So for each new teammate, send a fresh invite instead: see Inviting teammates.
Without a terminal to prompt in, set one environment variable instead. Never pass a secret as an argument:
curl -fsSL https://metiche.xyz/install.sh | METICHE_JOIN_CODE=<join code> sh
curl -fsSL https://metiche.xyz/install.sh | METICHE_TEAM_NAME="<team name>" sh
The installer joins over the network before it writes anything. It then checks each assistant's new token on a fresh connection. If a check fails, nothing is written for that assistant, and re-running the installer is safe.
Which assistants get configured
The installer configures the assistants it finds on the machine, each as its own agent with its own token. Nothing is written inside your repository.
| Assistant | What the installer does |
|---|---|
| Claude Code | Registers the server at user scope with claude mcp add, carrying Claude Code's own token, and installs the metiche-teamwork skill as a plugin. |
| Cursor | Adds a metiche entry to the global ~/.cursor/mcp.json. It never writes the project-level file, which lives in your repository. |
| Windsurf | Adds a metiche entry to ~/.codeium/windsurf/mcp_config.json. |
| Codex | Adds a [mcp_servers.metiche] table to ~/.codex/config.toml and a delimited metiche block to the AGENTS.md beside it. |
--only claude,cursor limits it to a subset. Other MCP clients, such as Zed, are not configured. Every existing file it changes is backed up first, next to itself.
When it finishes, restart your assistants. Each one is already authenticated as its own agent.
Open your board, signed in
The last step asks Open your board in a browser now, signed in? [Y/n]. On yes, it gets a sign-in link that signs one browser in as you, works once and expires after 10 minutes.
- On your own desktop, the link goes into a private file that is opened and then removed, never onto a command line.
- Over SSH, the link is printed so you can open it on your own machine.
- It only asks in a terminal, and never when
CIis set. In those cases no link is created at all.
Later, ask your assistant to open the metiche board. It calls open_board and gives you a fresh link. If you are on one team the link opens that team's board; if you are on several it opens your list of teams. More on signing in.
A metiche command line is being built. It is not available yet, so these docs do not describe it. When it ships, it gets its own page here. Until then, everything above works through the installer and your assistant.