Use it when the agent works in a terminal on your machine, or you want what only the CLI has: syncing your wiki to a folder, files over 10 MB, imports and exports.

How it works

slipdock is a command-line client for everything the API does: boards, cards, comments, the wiki, files (slipdock attach and slipdock download), search, automations and runners. It saves the server's address and your token, so neither you nor the agent has to repeat them, and its output is easier to read in a transcript than raw JSON.

It's an Elixir escript, so the machine that runs it needs Erlang/OTP. That's why nothing else on this page depends on it.

Every command

The command reference lists every command by group, with a filter to find one by name. It is made from the same text slipdock help prints, so it never falls behind the CLI, and is easier to search than a terminal.

Install it

On Linux and macOS, into ~/.local/bin/slipdock. It needs Erlang/OTP 27 or later, and if there is none it says what to install (brew install erlang on a Mac) rather than running anything as root. It checks the download against /cli/SHA256SUMS and the release key's signature (with ssh-keygen):

curl -fsSL https://app.slipdock.us/cli/install.sh | sh slipdock auth

That is /cli/install.sh, the CLI; /install.sh without /cli/ installs the skills.

On Windows, in PowerShell. This installs Erlang through winget if it isn't already there:

irm https://app.slipdock.us/cli/install.ps1 | iex slipdock auth

A server built from source serves no signature, and with none (or no ssh-keygen to check it) both install nothing and say why. To install its CLI on the checksum alone, add | sh -s -- --allow-unsigned, or on Windows set $env:SLIPDOCK_ALLOW_UNSIGNED = '1' first.

From a checkout, build it from the repository (Elixir 1.17 or later):

cd cli && mix escript.build && cp slipdock ~/.local/bin/ slipdock url https://app.slipdock.us slipdock auth

slipdock auth uses the same sign-in as the guide: it prints a code and you approve it in the browser. slipdock url with no argument shows which server it's pointing at, which is the first thing to check when it can't connect.

What it has that MCP doesn't

  • slipdock sync mirrors your wiki to a local folder and keeps the two in step, so you can edit pages in Obsidian or any other editor; slipdock sync from-server and slipdock sync to-server run a pass one way only.
  • slipdock attach uploads files up to 250 MB, recordings included, where MCP takes up to 10 MB.
  • Importing and exporting boards and pages, including from Trello.
  • slipdock skills install and slipdock skills check keep the skills up to date, and slipdock tools install and slipdock tools check do the same for a Tool's skills.
  • slipdock tools publish packs a folder and publishes it as a Tool.

Good to know

  • $SLIPDOCK_URL and $SLIPDOCK_TOKEN override the saved address and token for a single command, such as one run against another server.
  • slipdock guide prints the short agent guide, which ends with the names of its other sections; slipdock guide wiki prints one of them, and slipdock guide all the whole guide, which is long.
  • slipdock work lists what is waiting on you, and slipdock card on an epic and slipdock board print a Waiting on you: line for what in the tree is on you (waiting_on_me on get_card and get_board: count, cards with their reasons, on_others and line); an epic whose tree is all waiting on a person has nothing workable; slipdock wait and slipdock answer open and answer a wait on a person (--question once per question, --answer once per answer, --skip to move on without them, --kind the kind of question, which the board routes to its person; slipdock waits lists the ones asked before); slipdock pulse gives a board's flow numbers; slipdock pause and slipdock resume hold and release its runner work.
  • The skills use the CLI where it's installed and fall back to curl where it isn't.