Skip to main content
The developer page is the engineer’s counterpart to the savings dashboard. It renders the live in-memory state from SessionInspector, re-rendering on every GET and lost on process restart. 
GET /__telos/developer        # HTML
GET /__telos/developer.json   # JSON

​
Session list

Sorted by last_seen descending:
ColumnMeaning
session_idsession identifier; click to enter the detail view
modelthe ir.hints.model of the most recent request
harnessthe harness identified most recently (hermes / openclaw / passthrough)
callscalls observed (capped at INSPECTOR_HISTORY=25; oldest dropped beyond that)
tool callstotal tool_use blocks the assistant initiated
distinct toolsnumber of unique tool names
tool_result charscumulative character count of all tool_result content
last seenrelative time since the last call

​
Cache breakpoint slots (BP-*)

Anthropic allows only 4 cache_control breakpoints, cut by the priority below. Physical order is guaranteed by tools → system → messages, so the long TTL (1h) naturally precedes the short (5m).
SlotPositionTTLTrigger
BP-Tlast block of the tools segment1hthe request carries tools
BP-Slast PIN block of system1hsystem has a PIN block (excluding ref-pool)
BP-Rlast FOLD block of system1hsystem has a FOLD block (end of the ref-pool)
BP-midlast non-DROP block in messages[len-19]5mlen(messages) ≥ 19 (fixes R2)
BP-Xlast non-DROP block of the last message5ma non-empty message exists
Priority: BP-T > BP-S > BP-R > BP-mid > BP-X.

​
Prompt regions · band distribution

One stacked bar per segment (tools / system / messages), colored by band:
  • P (PIN) — gold: system prompt, tool defs, the main body of the user’s question
  • F (FOLD) — blue: ref-pool, previous-turn tool_result, assistant history
  • D (DROP) — gray: the per-turn envelope (<system-reminder>, <environment_info>, timestamps)
Each title shows the segment’s total chars plus (chars, blocks) per band, and a turn-over-turn delta (red +N = grew, green −N = shrank).

​
Recent calls

Each row is a snapshot of one call (most recent 25 retained):
ColumnMeaning
#call index (monotonic since session start)
latcall latency (seconds)
raw_in / cache_read / cache_write / outputthe normalized usage quadruple
tools / system / messages chars · Δper-segment chars + diff from last turn
plan slotsthe BP slot names actually placed this turn
uses / resultstool_use blocks this turn / tool_result blocks this turn
uses and results are off by one turn: the tool_use the assistant initiates in turn N generally waits until the turn N+1 user to have its tool_result sent back.

​
Latest IR · per-message blocks

A snapshot of TelosIR.messages for the most recent request, in message-index order. Each block is a pill like P·text 1,234c [openclaw/user-query]:
FieldMeaning
color / first letterband: P gold = PIN · F blue = FOLD · D gray = DROP
kindtext / tool_use / tool_result / thinking / image / tool_def
Ncblock payload character count
gray tailsource_tag or ref_slug — which harness rule carved this block

​
source_tag reference

The prefix of source_tag is the harness name; the suffix describes the slice source.
HarnessSegmentCommon tag
openclawtoolsopenclaw/tools
openclawsystemopenclaw/system-large / openclaw/system-ref-stub / openclaw/system
openclawmessagesopenclaw/tool-result / openclaw/assistant-text / openclaw/assistant-tool-use / openclaw/other
hermestoolshermes/tools
hermessystemhermes/system / hermes/file-block (<file path=…> ref-pool blocks > 2KB)
hermesmessageshermes/tool-result / hermes/assistant-text / hermes/assistant-tool-use / hermes/thinking / hermes/other
shareduser splitharness/user-query (PIN) · harness/system_reminder / command_message / command_name / env_info / current_time (DROP) · harness/prev_result (FOLD)
If you expect Claude Code (hermes) but see an openclaw/* prefix, _detect_harness likely misjudged — see Harness integration.

Savings Dashboard

The dollars-and-cents view for the rest of the team.