BKS open-bridge · live demoBKS open-bridge · Live-Demo

What a real session looks likeSo sieht eine echte Session aus

Four flows from the team that builds BKS open-bridge, replayed from BKS-Lab's own instance. Branding and work are real; client names are kept generic. The formats are exactly what a live session prints: the morning greeting, the briefing dashboard, an incident handed to a specialist, and first-run onboarding. Vier Abläufe vom Team, das BKS open-bridge baut, abgespielt aus der eigenen Instanz von BKS-Lab. Branding und Arbeit sind echt, Kundennamen bleiben generisch. Die Formate sind genau das, was eine echte Session ausgibt: die Morgenbegrüßung, das Briefing-Dashboard, ein Vorfall, der an einen Spezialisten geht, und das Onboarding beim ersten Start.

What you are looking atWas du hier siehst A replay, not a live connection: the session is typed out as text in your browser. Hover the terminal to pause it, click it to skip ahead. Eine Wiedergabe, keine Live-Verbindung: die Session wird als Text in deinem Browser getippt. Maus aufs Terminal hält an, ein Klick spult vor.

Prefer to watchLieber ansehen The 1:25 film on YouTube shows the same morning as a video. This page itself stays free of third-party requests. Der Film (1:25) auf YouTube zeigt denselben Morgen als Video. Diese Seite selbst lädt nichts von Dritten.

  1. Morning Session start: a briefing, not a status dump.Sessionstart: ein Briefing statt einer Statusliste.
  2. Briefing /briefing: a 76-column dashboard from plain Markdown and YAML./briefing: ein Dashboard mit 76 Spalten aus schlichtem Markdown und YAML.
  3. Operator Incident to code fix: test first, shipped to UAT, stops at the prod gate.Vom Vorfall zum Code-Fix: Test zuerst, nach UAT ausgeliefert, Halt vor dem Prod-Gate.
  4. First run Onboarding on a fresh clone, each step gated on your yes.Onboarding auf einem frischen Klon, jeder Schritt wartet auf dein Ja.
bks · your-bridge

Click the terminal to skip ahead Klick ins Terminal, um vorzuspulen

① Morning: session start

$ cd ~/Developer/bks/your-bridge
⚡ Good morning, Alex. 🔥 5d 🔔 2
▸ BKS-Lab · your-bridge · user/alex
your-bridge user/alex ↑3 ±6
⟳ docs(BKS open-bridge): launch strategy + live demo (1h ago)
◆ 11:00 Weekly · BKS-Lab · 45m
◆ 14:00 Launch review · BKS open-bridge live demo · 60m
🔴 2 waiting for your review ⚠ WIP 5/5
┌─ Doing · BKS-Lab ─────────────────────────────┐
│ ● open-bridge-launch distribution + live demo │
│ ● bridge-deck calendar timeline view │
│ ● bks-news weekly briefing automation │
│ +2 more │
└───────────────────────────────────────────────┘
$ claude
<bridge-phase0>
state=NORMAL · branch=user/alex · config=yes
3 CORE commits ahead: offer `git merge development`
</bridge-phase0>
> good morning
Morning. Three things since last night:
1. 02:14, CI went red on BKS open-bridge main: the release publish step
flaked. Same failure you fixed Tuesday. That fix never reached main.
2. Pages deploys from main, so the live demo hasn't rebuilt since 02:14,
and your 14:00 launch review walks exactly that page.
3. PR #61 (bridge-deck) hits day 4 today: your own three-day review
rule fired yesterday.
Suggest: merge the retry fix first (~15 min), and Pages rebuilds well
before 14:00. Demo prep second, #61 review after. Want the diff summary?
> what did I fix on tuesday?
One row from work/log.md, Tue 24.06:
| 14:32 | 🔧 | BKS open-bridge | release publish flaked 3×: pinned retry backoff in release.yml. Config, not code. |
Same root cause, red on main since 02:14. The pin never left
fix/release-retry. One merge and tonight's 02:14 run is green again.

② /briefing: the daily dashboard

> /briefing
╭──────────────────────────────────────────────────────────╮
│ Week 26 · Tue 24 Jun · 09:02 │ Doing: 5 │ ⚠ 2 │
│ Focus: ship the BKS open-bridge launch demo → open the repo │
╰──────────────────────────────────────────────────────────╯
── ⚠ Warnings ──────────────────────────────────────────────
🟡 WIP 5/5 at cap; close or reclassify before new work
🟡 Tailscale node-key expires in 18 days
── Focus today ─────────────────────────────────────────────
💻 open-bridge-launch distribution + live demo 🟢 doing
🔧 bridge-deck calendar timeline view 🟡 doing
📝 bks-news weekly briefing automation 🟢 doing
── GitHub (BKS-Lab) ────────────────────────────────────────
Agents & MCPs #20 4 open · 1 in review
BKS Operations #25 3 open
── Open PRs (2 human · 1 bot) ──────────────────────────────
#61 calendar timeline bridge-deck ↑ sam 1d
#18 launch demo BKS open-bridge ↑ alex 3h
── Activity (7 days) ───────────────────────────────────────
44 commits: BKS open-bridge 24 · bridge-deck 13 · bks-news 7
── Calendar today ──────────────────────────────────────────
◆ 11:00 Weekly · BKS-Lab · 45m
── Next steps ──────────────────────────────────────────────
[ ] merge development (3 commits ahead)
[ ] review PR #61 (bridge-deck) → then it can land
[ ] renew the Tailscale node-key before it expires

③ Operator: find the bug, TDD the fix, ship

> inbound invoices aren't booking, what happened?
Loading the e-invoicing ops playbook. Dispatching the log-analyst against
the last 3h of fn-invoicing-in-prd logs (read-only, isolated).
◐ Task · subagent_type=log-analyst · running …
◇ log-analyst → returned
Summary NEW BLOCKER: inbound parse fails in prod since 08:31 UTC; docs stuck in retry
Scope last 3h · fn-invoicing-in-prd · 1,120 hits
Clusters 🔴 parse_error @ map_invoice 54× 08:31→now NEW
Correlation doc_8842: received OK · parse FAIL @ map_invoice · never booked
Root cause payment_means code "59" (SEPA DD) missing from the enum → KeyError aborts the pipeline
That's a code bug in invoicing-service, not the operator. Fixing it test-first.
▸ red (a test that reproduces doc_8842)
+ tests/test_payment_means.py::test_sepa_dd_59
▸ pytest -k payment_means
✗ 1 failed (KeyError: '59') ← reproduced
▸ green (minimal fix)
~ invoicing-service/mapping.py · payment_means via .get(code, OTHER)
▸ pytest · ruff · mypy
✓ 214 passed · ruff ✓ · mypy ✓ · coverage 100%
▸ ship
✓ commit a3f1c9 · branch fix/payment-means-59 · pushed · PR #87
✓ deploy uat → fn-invoicing-in-uat · health ok
✓ replayed doc_8842 on UAT → booked
Done: off-spec SEPA-DD code "59" hit an enum with no fallback → KeyError, so every
inbound aborted. Test-first fix red→green, full suite + lint + types pass,
shipped to UAT and replayed doc_8842. It books cleanly now.
Prod deploy + PR #87 merge are your call. Ship it? [y/n]

④ First run: onboarding

> hi
Hi, I'm ELOPe, the AI running this bridge: your command hub for
agents, repos and standing orders, and I remember every session.
Fresh clone, nothing wired up yet (a 5-minute, reversible fix). I'll:
1. spin up your user/alex branch (keeps your data out of CORE)
2. scan your projects folder and map the BKS-Lab ecosystem
3. pick a theme and wire up your first agents
[y] Let's go [t] Tell me more [n] Not now
> y
Great, about 5 minutes. [A] Identity
Name → detected "Alex" from git config. Keep it? [y/edit]
GitHub → bks-lab · Projects → ~/Developer/bks
✓ created + checked out branch user/alex
[B] May I look at your setup? (names + structure only, never content)
✓ developer repos across two org folders
✓ homebrew gh, az, rclone, restic, tailscale, pandoc
✓ azure-cli logged in · 1 subscription
✓ tailscale 4 devices: mac-mini, macbook-pro, +2
[C] Based on what I found:
① rclone + restic detected → enable backup topology? [y/m/l]
✓ infra/backups/topology.yaml scaffolded · backup skill on
② tailscale (4 devices) → scaffold infra/remotes/? [y/m/l]
✓ infra/remotes/ scaffolded · 4 machines registered
✓ Onboarding complete. Your bridge is live. See you tomorrow, Alex.

The live instance of BKS-Lab, the team behind BKS open-bridge. Branding, repos and stack are real, though chapter ④ shows an earlier onboarding revision (see note above); client names are kept generic and there is no customer data, no secrets, no PII. Formats mirror the live briefing, session-start, coordinator/sub-agent and bridge-onboard flows. Die echte Instanz von BKS-Lab, dem Team hinter BKS open-bridge. Branding, Repos und Stack sind echt, Kapitel ④ zeigt allerdings einen früheren Stand des Onboardings (siehe Hinweis oben). Kundennamen bleiben generisch, und es gibt keine Kundendaten, keine Secrets, keine personenbezogenen Daten. Die Formate folgen den echten Abläufen von briefing, Sessionstart, Koordinator mit Sub-Agent und bridge-onboard.

This was the terminal. The same Bridge also has a page in the browser, the cockpit, and its demo runs live with invented data.Das war das Terminal. Dieselbe Bridge hat auch eine Seite im Browser, das Cockpit, und seine Demo läuft live mit erfundenen Daten.

The cockpit, an early version (alpha). The Bridge's own page in the browser: briefing, inbox and tasks, agent tabs, sessions and tokens. Below runs the real page with invented data. Click the tabs, open a row, ask the chat; the demo itself sends nothing.Das Cockpit, eine frühe Version (Alpha). Die eigene Seite der Bridge im Browser: Briefing, Posteingang und Aufgaben, Agent-Tabs, Sitzungen und Tokens. Unten läuft die echte Seite mit erfundenen Daten. Klick die Tabs durch, öffne eine Zeile, frag den Chat; die Demo selbst sendet nichts.

Live demo. Invented data, served from this site: the demo talks to no other host and saves nothing. The real cockpit runs on your own computer and answers only on 127.0.0.1.Live-Demo. Erfundene Daten, ausgeliefert von dieser Seite: die Demo spricht mit keinem anderen Host und speichert nichts. Das echte Cockpit läuft auf deinem eigenen Rechner und antwortet nur auf 127.0.0.1.

Get startedLoslegen

One prompt. Your own private bridge.Ein Prompt. Deine eigene, private Bridge.

Liked what you saw? Set up your own: one prompt to your agent creates a private copy and walks you through onboarding.Gefällt dir, was du siehst? Richte deine eigene ein: Ein Prompt an deinen Agenten legt eine private Kopie an und führt dich durchs Onboarding.