a pocket command deck

the connection

Niobium uses Hermes’ WebSocket JSON-RPC gateway. Gateway tokens stay in iOS Keychain or Android Keystore. The app discovers runtime capabilities and reports unavailable operations instead of inventing a successful result.

Model changes and Stop controls use the gateway’s current session revision and execution generation. Resumed chats recover their running state and pending approvals.

bot mode

A Pixel is a Hermes profile. Opening it returns to its canonical Bot Chat. @mentions identify teammates; Hermes handles attributed inter-agent messages. Group rooms run on a capable gateway and can continue after the phone disconnects.

Each Pixel’s appearance and companion are stored with its profile metadata. Cached 48×48 portraits use nearest-neighbour display, keeping the roster sharp and inexpensive to draw.

companions

The parent Pixel decides when a task benefits from delegation. Niobium shows the real child task, goal, status, tool count and available transcript. A correction is labelled queued until the backend delivers it. Failed delegations stay visible.

scope

Hermes has a larger feature surface than Niobium currently exposes. Sessions, tools, skills, MCP inventory, routines, rooms, photos and dictation are implemented to varying depth. Connector account flows, memory editing, project management, complete attachment support and background delivery still need work. See the method audit for the current detail.