Install Yaks

Run this in your project to give your agent the eris-yaks skill, then ask it to set up Yaks. The steps below are the manual path.

The skills CLI needs Node.js 22.20 or later; eris runs on bun (bun.sh).

Manual setup

1. 1

   Check for bun

   Your agent

   eris is TypeScript that runs on bun. If bun --version prints nothing, install it from bun.sh first.

   • $bun --versionCopied

   Expect: A version number.

2. 2

   Run eris

   Your agent

   Run eris straight from npm. To give your agents an eris command in every session, add the same package globally with bun.

   • $npx @sibylline-labs/eris@latest --versionCopied
   • $bun add -g @sibylline-labs/erisCopied

   Expect: eris followed by a version.

3. 3

   Connect Linear

   You, in the browser

   Open dash.sibylline.group and choose Sign in with Linear. Install the Yaks app into your workspace when prompted; a Linear admin does this once per workspace.

4. 4

   Create a CLI token

   You, in the browser

   In dash, open Connect your CLI and create a token. Add the two values it shows, ERIS_YAKS_TOKEN and ERIS_YAKS_URL, to your shell profile (for example ~/.zshrc) and open a new shell.

   • $eris yak --helpCopied
5. 5

   Send a test yak

   Your agent

   Send one yak. A delivered yak prints recorded: <id>, and a [Yak] issue appears in your Linear Triage. A WARN line means it wasn't delivered; its slug names the fix, usually the token or URL from the previous step.

   • $eris yak suggest --summary "First yak from this repo" --body "Testing the Yaks pipeline end to end."Copied

   Expect: recorded: <id>

6. 6

   Teach every session to file

   Your agent

   Add this block to your repo's AGENTS.md (and CLAUDE.md if you use one), or to your global agent instructions, so every session knows when to file.

   ## Yaks
   
   When the tooling fights back, file a yak and keep working. A yak is a side channel: it never blocks the task.
   
   - `eris yak issue`: something in the harness is wrong (a hook blocks a legal edit, a doc names a flag that doesn't exist, a command fails silently).
   - `eris yak suggest`: something could be better, and nothing has to be broken (a flag, skill or rule you wished existed; a workaround you've hand-rolled more than once).
   - `eris yak fatal`: the tooling broke and the task already stopped.
   
   Each takes `--summary "<one line>"` and `--body "<what happened, what you expected>"`; add `--repro "<command>"` when one shows it. Filing is deduplicated, so a repeat adds weight to an existing issue. File in the turn you notice.

   Copy