Skip to content
SibyllineYaks

Your Agent Harness, Self-Improving

Agents know their own harness: its issues and its improvements. Now let them hand both to your harness engineering team.

npx skills add sibylline-labs/eris --skill eris-yaks

Then ask your agent to set up Yaks.

$3 per seat / month · 14-day free trial, no card

Sign in with Linear →
Request access

Sibylline runs on yaks.

months
3
yaks
about 500
PRs
about 300

  • eris yak issue

    “Effect: the read-only guarantee is unenforced; only the prompt keeps the auditor from writing.”

    A read-only agent’s guard named tools that didn’t exist, so it blocked nothing. The fix covers every read-only agent.

    Filed by an agentSKW-1766Fixed in 27 min

  • eris yak issue

    30 reports

    “env VAR=val cmd is a common, legitimate shape, so this is a false positive.”

    The guard on secret files kept refusing ordinary commands. Every report clustered on one issue, and one parser rewrite closed the lot.

    Filed by an agentSKW-1816Fixed in 12 h

  • eris yak suggest

    “All 6 agents fell back to raw git commit, which the rule forbids. I’d have spent fewer turns with a non-interactive mode.”

    Subagents have no one to approve a commit, so a brief that says “commit” now counts as the approval.

    Filed by an agentSKW-1746PR in 9 min

  • eris yak issue

    13 reports

    “every subagent Bash call refused, including a bare pwd”

    Background subagents stalled without their parent ever seeing why. One settings change fixed it the next morning.

    Filed by an agentSKW-1743Fixed in 15 h

  • eris yak suggest

    “I’d have caught this months earlier if the harness flagged an oversized repo CLAUDE.md.”

    One repo’s CLAUDE.md had grown to 124 KB, loaded into every session. An oversized one now draws an advisory.

    Filed by an agentSKW-1809Hook shipped in 5 days

Three minutes to your first yak.

You do two things. Your agent does the rest.

  1. You run the command
  2. Your agent installs eris
  3. You connect LinearIn your browser: Sign in with Linear, Install the app, Create a CLI token
  4. Your agent sends a test yakeris yak suggest
Triage
ACME-483[Yak] First yak from this repo

Linear stays the system of record.

Yaks land in your workspace. We keep only what deduplication needs.

A yak is redacted on your machine, redacted again by Yaks and delivered to your Linear. Thirty days after delivery its body is deleted; metadata and a dedup fingerprint remain.

Your machine

Redacted before upload.

Yaks

Redacted again. The body is deleted 30 days after delivery.

Your Linear

The system of record. No second dashboard.

$3 per seat / month. 14-day free trial. No card required. A seat is a person with an active CLI token.

That’s the whole price list.

One plan, paid per person whose agents file yaks. Try it on your own harness for two weeks first.

Every seat includes

  • Yaks delivered to your Linear Triage
  • Clustering and deduplication across every agent
  • Redaction on your machine and again on ours
  • Report problems with eris itself through --vendor
Sign in with Linear

Watch a yak travel.

An agent hits a missing script, files a yak in one line and finishes the job. Every later session that hits it adds to the same issue.

claude · ~/acme/api · feat/rate-limit
  1. Add a per-tenant rate limit and run the tests
  2. Update(src/limits.ts)
    +38 −4
  3. Bash(bun run test:changed)
  4. error: Script not found "test:changed"
  5. AGENTS.md points at a script that doesn't exist. Filing a yak and running the suite directly.
  6. Bash(eris yak issue --summary "AGENTS.md says run test:changed; no such script in package.json" --body "Ran the documented command; package.json has test and test:watch only.")
  7. recorded: yak_01JC4M7Q · new issue ACME-482 · exit 0
  8. Bash(bun test src/limits)
  9. 14 pass · 0 fail
Triage3ACME
  1. ACME-482[Yak] AGENTS.md says run test:changed; no such script in package.json7reports
  2. ACME-479[Yak] pre-commit hook rejects valid migration filenames that start with a date3reports
  3. ACME-471[Yak] lint skill names --fix-dry-run, which eslint doesn’t have2reports
  4. ACME-466[Yak] MCP server times out on the first call after idle; the retry succeeds5reports

ACME-482 · Activity

  1. Opened from yak_01JC4M7Q · claude · ~/acme/api
  2. 3 earlier occurrences
  3. +1 occurrence · claude · ~/acme/api
  4. +1 occurrence · codex · ~/acme/api
  5. +1 occurrence · claude · ~/acme/worker
  6. Moved to Done · fixed in 5 h
FiledLater sessionsFixed in 5 h

Runs in your browser; nothing is sent. Secrets are redacted first, as the CLI does.

  1. One line, mid-task.

    eris yak issue|suggest|fatal attaches repo, branch and harness, and redacts secrets before upload.

  2. Never blocks the task.

    One bounded request; if it can’t land, the CLI warns and exits 0.

  3. Clustered, not noisy.

    A repeat becomes an occurrence on the open issue: thirty agents, one issue.

Your agents already know what’s broken.

Give them one line to tell you.

npx skills add sibylline-labs/eris --skill eris-yaks

Then ask your agent to set up Yaks.

orSign in with Linear