theboringfloor

README

theboringfloor

A startup office in your terminal, staffed by real agents.

Chat with the boss. Watch the floor — employees walk, type, drop mail, hit the tea machine. Right panel is yours. Left pane is the floor (or the in-TUI browser).

Website · Docs · Get started · Discord

Under the wallpaper it is real: the manager is Oikonomos, employees are opencode sub-agents, the board is agentmemory actions, mail is agentmemory signals.

Install

One-liner — binary plus agentmemory as a reboot-safe service:

curl -fsSL https://boringfloor.com/install.sh | sh

Windows (PowerShell):

irm https://boringfloor.com/install.ps1 | iex

The Windows installer downloads the matching release archive, verifies its SHA-256 checksum, and installs theboringfloor.exe (plus tbo.exe) in %LOCALAPPDATA%\theboringfloor\bin. It adds that directory to your user PATH; open a new PowerShell window, then run theboringfloor --demo. To install manually, download the matching Windows .zip and checksums file from Releases, verify the checksum, then put theboringfloor.exe in a directory on your PATH.

Pick the LLM transport at install (opencode default; claudecode needs the claude CLI):

curl -fsSL https://boringfloor.com/install.sh | sh -s -- --backend claudecode

Then:

theboringfloor            # live office
theboringfloor --demo     # touring mode
theboringfloor --version  # stamp: version, commit, date

Pin a tag, or grab a prebuilt (macOS/Linux/Windows, amd64/arm64) from Releases:

go install github.com/theboringhumane/theboringfloor/cmd/theboringoffice@latest
ln -sf "$(go env GOPATH)/bin/theboringoffice" "$(go env GOPATH)/bin/theboringfloor"

Full on-ramp: Getting started · local notes in docs/.

Docs

Manual lives on the site. This repo keeps a thin index so GitHub readers land in the right room.

In-repo	Website
Docs hub	Docs home
Architecture	Vision
Website	Get started
Commands (cmd/)	Sounds
Scripts	Blog

Manual (site)

Install & setup

• Getting started — curl, demo, live office, --session

Core

• Backends — opencode or claudecode, both primed with the same manager charter
• Chat & work threads
• Plan mode

Workflow

• Permissions & questions
• Queue, board & memory

Panels & reference

• Terminal & git tabs
• Browser tab
• Layout, themes & power
• Keys & slash commands

Config file: ~/.theboringfloor/configs/brain.json (theboringfloor --print-default-config). Details: backends + layout.

Whichever backend you pick, the office primes it with the same manager charter before the first turn: the bundled oikonomos protocol lands at .opencode/oikonomos.md in the served directory. On opencode the office merges ./.opencode/oikonomos.md into .opencode/opencode.json's instructions — a field-preserving merge, every other key survives. On claudecode it writes CLAUDE.md: created with @.opencode/oikonomos.md when absent, or — when you already keep one — an idempotent <!-- theboringfloor charter --> block appended below your content. Nothing member-owned is ever overwritten.

Peek

Keys

One line per key — the full table lives at keys & slash commands.

Agent plan tools

In plan mode, the boss can present or refresh the plan pane with explicit markers. These are agent-only protocol lines, not commands for members to type:

⟦plan-present⟧
# Goal
Add the requested capability.

# Steps
1. Inspect the current flow.
2. Make the focused change.
⟦/plan-present⟧

⟦plan-update⟧
# Goal
Add the requested capability with the clarified edge case.
⟦/plan-update⟧

plan-present and plan-update are multiline blocks. They fill the existing plan pane as a draft; they do not run work and they never bypass your approval. Review or edit the draft, then press ctrl+x twice to approve it. Only that second confirmation sends the plan to the build agent.

Once you have approved a plan, the office keeps that approved version across sessions (up to 20,000 runes). Later drafts and updates stay drafts: they do not replace the approved plan until you review and approve them. When the boss needs the current decision, it places this marker on its own line:

⟦plan-get-approved⟧

The office sends the latest approved plan back to the boss. If there is no approved plan yet, it does not substitute a draft.

Key	Does
tab / shift+tab / 1..7	switch the right panel: chat · terminal · agents · board · mail · activity · git
ctrl+b	flip the left pane: floor ↔ browser
enter	send to the boss — free-sends into the backlog while it's busy
shift+enter / ctrl+j	newline in the chat input
@	attach-file picker — type to filter, enter/tab attach
ctrl+v	paste text — attaches the image instead when the clipboard holds one
big paste	chat pastes >20 lines or >2000 chars collapse to a [pasted N lines · M chars] chip — one backspace unit, full text sent on submit
/model · /session · @	pickers filter as you type — N/M badge, esc clears the filter, then closes
y a n esc	answer a permission prompt — allow once / always / reject / defer
click a tool row	expand what the tool returned (all kinds — capped, tail-kept; no output as such when there's none)
⟦recent-messages⟧ / ⟦recent-messages: N⟧	agent-only context recovery marker — on its own line once per reply; sends the boss the latest 20 messages by default, or N clamped to 1..50
/bypass	toggle bypass-permissions mode — session-only, confirm-on-enable, ⚠ BYPASS rides the topbar while on
ctrl+x twice	plan mode: confirm and approve the current draft for the build agent
ctrl+q	arm quit — works everywhere

/bypass is the deliberate escape hatch. Enabling asks for an explicit confirm — agents will run tools and browser actions WITHOUT asking, this office session only — disabling is instant. While on, every tab's topbar carries a loud ⚠ BYPASS segment, backend permission asks stop (claude spawns with --dangerously-skip-permissions; the office-owned opencode process gets an ephemeral OPENCODE_CONFIG_CONTENT={"permission":{"*":"allow"}} override), any stray ask is auto-approved with a dim log row, and the office's own browser-action prompt is skipped the same way. Toggling builds and starts a fresh backend before switching; the current backend stays usable until the replacement is live, and claude resumes your session context. Every boot starts with bypass OFF. brain.json, .opencode/opencode.json, and the parent process environment stay untouched.

If the boss loses context after compaction, it can place ⟦recent-messages⟧ (the default 20) or ⟦recent-messages: N⟧ (1..50) on its own line, once in a reply. The office removes the marker and sends a read-only synthetic follow-up containing recent user, boss, and tool transcript entries — newest content preserved, capped at 12KB — then shows context: sent N recent messages to the boss. It never asks permission.

Browser tab (the left pane, behind ctrl+b):

Built-in browser first. Members open a page with /open <url>. Agents put one of ⟦open-browser: URL⟧, ⟦browser-screenshot: URL⟧, or ⟦browser-snapshot: URL⟧ on its own line: open a page, render a PNG for the member, or read its text and links back to the agent. ⟦browser-action: URL | click: CSS-SELECTOR⟧ (or fill / eval) changes a page and is permission-gated. The built-in directives work for localhost and external https:// pages; agents use Chrome/Chromium, Playwright, Puppeteer, or a terminal browser only when the member explicitly asks, or when the built-in path fails and they explain why.

Key	Does
↑/↓ or j/k	move the link cursor
o	open the focused link
e	edit the URL inline in the location bar — prefilled, enter opens, esc cancels
O	open the current page in the OS browser
[ / ]	back / forward, 100-page history ring
r	reload in place
pgup / pgdn	scroll the body
q / esc	back to the floor

On kitty/ghostty with Chrome, pages render as headless screenshots — shot badge, PNGs under ~/.theboringfloor/shots/ — and the boss can screenshot pages for you, snapshot pages to read for itself, and (with your approve-once permission) click, fill and eval on them. Pastes into the terminal tab reach the shell bracketed-paste-wrapped. Everywhere else the browser is text on purpose.

Community

 

Join the Discord — floor talk, backends, bugs, shots.

Office memory rides agentmemory. Install script wires it, or npm install -g @agentmemory/agentmemory.

Commits through the office can stamp Co-authored-by: TheBoringMajdoor — scripts.

License

MIT © theboringhumane / theboredteam