Coming onlinePRODUCT & ENGINEERING OPS

Gotthard Triaged and reviewed. Never merged.

Gotthard reads your GitHub repositories and your Linear workspace, cites two things for every finding, and posts only what you approved.

Gotthard is built and not live yet. It goes live when it passes its go-live check, one agent at a time, and this page will say so when it does. Dom, Säntis and Eiger are ready to work — start with those. Gotthard cannot be hired yet.

WHAT IT HANDS YOU

Proposed, reviewed,
never merged.

01Triage

Triage

Your own labels, a priority, a likely duplicate and an owner, proposed for each new issue.

Sample

#513 A typo in Settings
docs · P4
Proposed

#512 Export to CSV
feature · P3
Proposed

#511 Login loop on Safari
bug · P1 · duplicate of #482
Proposed

Nothing postedPosted only after your approval

02Pull request review

Pull request review

Line by line, against your conventions. Comments are drafted; it never approves and never merges.

Sample

PR #219 · bank sync retries
Gotthard · review
Not merged

api/bank-sync.ts-  return fetch(url)
+  return retry(() => fetch(url))

This retries without a limit. Cap it at three attempts, as api/client.ts does.

api/client.ts

3 comments drafted

03Changelog

Changelog

Drafted from the pull requests merged since your last release, for you to approve and post.

Sample

Changelog · v1.4

  • Fixed: the login loop on Safari (#482)
  • New: export any report to CSV (#205)
  • Faster: the bank sync retries at most three times (#219)

Changelog · v1.4
Gotthard · from 11 merged pull requests
Draft

Posted after your approval

Everything it owns

WHAT IT OWNS

  • Issue triage: your existing labels, a priority, a likely duplicate and a suggested owner
  • Steps to reproduce a bug, proposed from the issue and the code. It runs nothing
  • Reviews a pull request, every point citing the file and line, posted as a comment on it — never an approval
  • The changelog, drafted from merged pull requests
  • A weekly engineering digest
  • Labels on GitHub; comments and new issues on Linear. Posted only after your approval

ROUTINES IT SHIPS WITH

  • Engineering digestEvery Monday at 08:30: what was merged, what was opened, what is still unlabelled, and what Gotthard proposed.
  • Triage when you askPoint it at new issues and it proposes labels, a priority, a duplicate and an owner, each as an approval.
  • ChangelogDrafted from the pull requests merged since your last release, for you to approve and post.
2
SOURCES BEHIND EVERY FINDING
0
MERGES
0
ISSUES CLOSED

An illustration. The company, the names and the figures are examples.

IN YOUR CONTROL

You hold the line,
and the passkey.

Scoped connections you grant and can revoke. Zuger never holds your passwords.

How the approval gate works

The line

  • Money leaving any accountAlways stops
  • Anything reaching a customer or candidateAlways stops
  • Changing a mandate or a thresholdAlways stops
  • Internal handoff between agentsRuns freely

Approve with your passkey

PR #219 reviewed3 comments drafted · not merged

Only what you connect

  • GitHub your own repositories
  • Linear your own workspace

Zuger can’t move money, run payroll, sign or file through any connection.

Revoke in one tap

    Disconnect a tool and its token is deleted at once. What was already synced stays with your company until you delete it.

  • GitHub your own repositories
  • Linear your own workspace
  • Read again by Bernina

    • pre · pass
    • in-run · pass
    • post · pass

    Three verdicts, before you see anything.

    THE LINE IT NEVER CROSSES

    What it will never do without you

    2SOURCES BEHIND EVERY FINDING
    0MERGES
    0ISSUES CLOSED
    • Merge, or push code to any branch
    • Approve a pull request
    • Close or delete an issue, a pull request or a comment
    • Deploy anything
    • Post anything you have not approved

    TRY IT

    Triage an issue.

    A new issue arrives. Watch Gotthard propose labels, then approve them with a simulated passkey.

    DEMONothing leaves this page.

    #511 Login loop on Safari

    opened today · no labels yet

    bugP1duplicate of #482owner: Lea

    A new issue came in.

    Gotthard proposes your own labels, a priority, a likely duplicate and an owner. It posts nothing yet.

    PROPOSED · NOTHING POSTED

    Labels proposed, with two sources.

    It reads the issue and #482, and cites both. Posting the labels waits for your passkey.

    Confirm with your passkey.

    A simulated passkey: this page asks your device for nothing.

    Posted, in this demo.

    In GitHub the labels would land on #511. The duplicate stays open: closing it is yours, and so is the merge.

    Gotthard never merges.

    Bernina reads it again.

    Before a Run starts, while it works, and before you see what it made. On every plan.

    Your passkey, at every gate.

    Anything binding waits for you, every time. An agent cannot read or change what stops it.

    ITS MANDATE, IN ONE LINE

    Triages issues, reviews pull requests and drafts the changelog. Posts only what you approved, and never merges.

    GotthardProduct & Engineering Ops

    PART OF THE ZUGER SUPER-AGENTComing soon

    What it finds,
    and who it works with.

    Zuger is the colleague you talk to. Each agent owns its part, and the work moves between them.

    Coming soon. Today Zuger works when you ask, or on a routine you set.

    Sample

    A pull request has waited 9 days for review

    Found by Gotthard

    GitHub · pull request 482Linear · issue ENG-311

    Prepared: a reminder to the reviewer, for you to post.
    Sample

    Three issues describe the same bug

    Found by Gotthard

    Linear · ENG-298, ENG-305, ENG-309GitHub · commit 4f2a9c1

    Prepared: one issue to keep and two to close, for you to approve.
    Sample

    Release 2.4 has no changelog yet

    Found by Gotthard

    GitHub · release 2.4Linear · cycle 18

    Prepared: the changelog, for you to publish.

    Sample findings. The companies, the names and the figures are examples.

    Works with

    • Releases worth a post go to Matterhorn.
    • Fixes that answer a customer go to Moléson.

    Channels

    • The Console
    • Claude and any MCP client
    • TelegramRolling out
    • WhatsAppComing soon

    Part of the Zuger super-agent.

    QUESTIONS

    Questions, answered.

    What does Gotthard do?

    Gotthard works in your GitHub repositories and your Linear workspace. It triages new issues with your own labels, a priority, a likely duplicate and an owner; proposes steps to reproduce a bug; reviews a pull request, every point citing the file and line, as a comment on it; and drafts the changelog from what was merged. Every finding cites at least two things it read. It posts a comment, an issue or labels only after you approve them with your passkey, and it never merges, pushes code, approves a pull request, or closes or deletes anything.

    Can Gotthard merge a pull request?

    No. It never merges, pushes code, approves a pull request, or closes or deletes anything.

    What does it post, and when?

    Labels on GitHub, comments and new issues on Linear, and its review as a comment on the pull request, and only after you approve them with your passkey.

    Does it run code to reproduce a bug?

    No. It proposes steps to reproduce from the issue and the code. It runs nothing.

    When does Gotthard go live?

    When it passes its go-live check, one agent at a time. This page will say so when it does. Dom, Säntis and Eiger are ready to work.

    Free plan · No card

    Gotthard is coming online.

    Dom, Säntis and Eiger are ready to work. Start free with Dom, no card. Gotthard joins them when it passes its go-live check.