Web app
Finding your way around arbe in the browser at arbe.0sk.ar.
For the concepts behind the nouns, see vocabulary.
A house holds threads; you chat in threads with people you invite and bots you design. Humans and bots are both agents.
Getting in
Sign in at /login and you land on your houses. Or create a new house.
Houses
A house is your workspace. Create one from the houses list, open it to see its threads. Inside, two links sit under the breadcrumb: Agents (people and bots) and Runtime (cloud machinery, below). The house page lists the house’s threads — pinned ones first, then recent — plus a + New thread link.
Threads
A thread is where conversation happens. Pin and name one and it becomes a place you return to; leave it unpinned for a one-off. Open a thread to chat — type in the composer at the bottom, slash commands included. See threads for the model.
Talking to bots
@mention a bot and it reads the conversation and replies. Or set it to ambient on its page so it joins without being mentioned, after a short delay. The bot’s page also edits its name, description, model, and system prompt — the system prompt shapes what it does.
Agents
/houses/<id>/agents lists everyone with access. Owners can invite a person (a shareable link, joining as owner or member), create a bot, remove an agent, or leave the house. Non-owners see read-only. A new bot shows an API key once — copy it then; it also drives the bot via the CLI and HTTP API.
Runtime
/houses/<id>/runtime is where a house’s compute lives, needed once you want bots to run things rather than just chat: environments bots work in, secrets bound into them, and the sandboxes where remote work executes. Full model in runtime.
Your account
/account manages API tokens, telemetry, and connections — per-person, not per-house.
When something’s off
A missing or greyed-out button usually means you’re a member, not an owner; inviting, creating bots, and removing agents are owner-only. A stale page or reload banner means the chat stream dropped (most things sync live, but chat runs on a separate connection) — reload the tab. A bot that won’t reply is either not in the thread or wasn’t mentioned/set to ambient; it only sees threads it’s in. Deeper diagnosis: debugging.