// Tools

xeroctl learnings

Read the distilled learnings the router captures after tool runs and chats: vector-indexed memories the pre-dispatch retriever uses to inform later runs. The CLI surface is narrow today: fetch one learning with show, and list a workspace's learnings through the execution API.

Availability: xeroctl learnings show fetches a single learning by id. There is no search or list subcommand yet; to list a workspace's learnings, call the execution API directly (see List a workspace).

Overview

The learnings command group provides CLI access to accumulated workspace learnings. Learnings are extracted automatically after tool executions and stored as vector-indexed memories that the pre-dispatch retriever uses to inform future executions.

Context-aware: learnings resolves the base URL, project id, and API key from the active xeroctl deployment. Pass --frontend-url to override for a one-off invocation.

Scope required: all learnings commands need an API key with the execution scope. See Scopes.

The --workspace flag accepts the workspace external id in the operator-facing form ws_<hex> (for example ws_8f2c1a04b9e7). Raw workspace UUIDs are not a user-facing surface and are not accepted here.

Usage Pattern

bash

xeroctl learnings show <lid> # Fetch one learning by id

show

Show full details for a single learning: the content body, source type, relevance score, and creation timestamp. Requires the execution scope (see Scopes).

bash

                    xeroctl learnings show lrn_01HXXXX
xeroctl learnings show lrn_01HXXXX -o json
                

Arguments

Argument	Description
`learning-id` (positional)	Learning external id (`lrn_<hex>`).

Response fields

ID, learning external id
Content, raw learning text
Workspace ID, workspace external id (when set)
Score, relevance score (when emitted)
Source Type, originating surface (tool / chat / operator)
Created, ISO 8601 timestamp

List a workspace

There is no learnings list subcommand yet. List a workspace's learnings through the execution API. The project id and API key are the same values the active deployment uses, and the call needs the execution scope.

bash

                    curl -sS \
  -H "Authorization: Bearer $XEROTIER_API_KEY" \
  "$XEROTIER_FRONTEND_URL/$XEROTIER_PROJECT_ID/v1/exec/learnings?workspace_id=ws_8f2c1a04b9e7"
                

Scopes

All learnings commands require an API key with the execution scope. The router rejects requests from keys without it with HTTP 403. See Authentication for the full scope reference.

Scope	Why it is required
`execution`	Required. Gates the XEM execution surface, of which the learnings store is a member.

Examples

Pipe a single learning into a downstream tool

bash

                    xeroctl learnings show lrn_01HXXXX -o json \
  | jq -r .content
                

xeroctl learnings

Overview

Usage Pattern

show

Arguments

Response fields

List a workspace

Scopes

Examples

Pipe a single learning into a downstream tool

xeroctl CLI

XEM Overview

Authentication