Skip to main content

Getting started as a Claway operator

How you reach the dashboard (OPS) depends on how Claway runs for you:

  • Claway Box: https://<box>/, the Box's address on your network. The first time, the Box asks you to activate it; see Getting started with Claway.
  • Hosted Claway: http://<server-ip>:8443/. Blockway sends you the address, your operator password and an authenticator QR code.

If anything is missing, stop here and email support@claway.io. We can reissue the password and the authenticator QR code; do not share them.

First login​

  1. Open the dashboard address in a fresh browser tab. On a Box, accept the browser's warning about the self-signed certificate for this address.
  2. If you have not done so yet, scan the authenticator QR code into your authenticator app (1Password, Authy, Google Authenticator, iOS Passwords). If your app supports labels, name it "Claway <org>" so you can find it later.
  3. Enter the operator password and the current 6-digit code, and sign in.
  4. Bookmark the dashboard address.

A tour of the pages​

These are the pages you will use most, in roughly descending order. The sidebar has a few more (Upstream, Controls, Handoff, Tasks, Cost, SLO, Webhooks, Users, Settings):

Overview — Hero stats: active sessions right now, messages per minute across all groups, the top three chats by volume today, most recent errors. This is where you land after login; if nothing looks alarming here, the rest of the pages can wait.

Events — WebSocket tail of everything the gateway is doing — inbound messages, agent runs, adapter state changes. Filter box supports substring matching against chat name, initiator, or action type. Useful when a customer says "Jarvis didn't reply to my message thirty seconds ago" and you want to see why.

Conversations — Per-chat timeline. Shows the agent's decision tree (what tool it called, what the tool returned, what the model said next), token usage per turn. Open this when a specific reply looked wrong; it is usually the fastest way to spot a persona rule that fired incorrectly.

Sessions — Recent agent sessions across all platforms. You can kill any session from here — useful if an agent gets stuck in a compression loop or starts loitering on a topic. Killing a session ends its short-term context window; the next inbound message starts fresh.

Personas — The heart of your job. One row per WhatsApp group. Clicking into a row opens a seven-tab editor: Identity, Skills, KB, Memory, Token usage, Files, History. See the persona guide for the deep dive.

Skills — The global skill catalog. You can toggle a skill on or off platform-wide, view what it does, and (from within a Persona) restrict which skills a specific group is allowed to invoke.

KB — Named knowledge-base collections. Create a collection, drop PDFs into it, then attach the collection to whichever groups are allowed to search it. Full details in the KB guide.

Memory — Per-chat MEMORY.md files. You can view and edit them with a diff preview. Rare to touch these directly — usually you'd let Jarvis manage its own memory — but useful when correcting a rememberd-incorrectly fact.

Connectors — The 31 messaging platforms Claway supports (WhatsApp, Telegram, Discord, Slack, Signal, BlueBubbles, Line, Teams, Email, …). Each row shows live health and has a Setup wizard button for the initial connect + a Manage dialog for day-to-day tweaks. The WhatsApp QR re-pair lives here — if you see the bridge stuck in AwaitingInitialSync, this is where you fix it.

Metrics — Token spend, latency p50/p95, fallback chain hits, embedding and rerank call counts. Useful for capacity planning and for the month-end conversation with Blockway.

Alerts — Subscriptions delivered via Telegram. Sensible defaults are already wired ("gateway down", "compression failure spike", "a chat has been silent for N hours"). Add tenant-specific ones from here.

System — Gateway, dashboard, and KB worker service health. Environment variable sanity checks (JARVIS_KB_DB_URL, OPENAI_BASE_URL, …). One-click restart for each service. The Env panel here is the first thing to look at when a KB upload silently fails or Jarvis says "I don't have kb_search".

Audit — Every write action (persona edit, KB upload, scope change) is logged here with initiator and payload. Export CSV streams the log for a date range — enterprise procurement or legal will ask for this eventually.

Housekeeping in your first week​

  • Add a real email under System → Support contact so alerts have somewhere to reply to.
  • Subscribe your on-call Telegram account to at least the "gateway down" alert.
  • Do one end-to-end test: send a message from an allow-listed group, watch it appear in Live Events, confirm Jarvis replies.
  • Book fifteen minutes with Blockway to walk through your first persona.

Anything else: email support@claway.io.