gitlore/docs/robot-mode-design.md

Robot Mode Design

Overview

Robot mode optimizes the lore CLI for AI agent consumption with compact JSON output, structured errors with machine-actionable recovery steps, meaningful exit codes, response timing metadata, field selection for token efficiency, and TTY auto-detection.

Activation

# Explicit flag
lore --robot issues -n 5

# JSON shorthand
lore -J issues -n 5

# Environment variable
LORE_ROBOT=1 lore issues

# Auto-detection (when stdout is not a TTY)
lore issues | jq .

Global Flags

Flag	Description
--robot	Force JSON output, structured errors
-J / --json	Shorthand for --robot
--quiet	Suppress progress/spinners (implied by --robot)
--fields <list>	Select output fields for list commands

Response Envelope

All commands return a consistent JSON envelope to stdout:

{"ok":true,"data":{...},"meta":{"elapsed_ms":42}}

Key properties:

• Compact JSON: Single-line output (no pretty-printing) for efficient parsing
• Uniform envelope: Every command wraps its data in {"ok":true,"data":{...},"meta":{...}}
• Timing metadata: meta.elapsed_ms is present on every response (wall-clock milliseconds)

Error Output Format

Errors are JSON on stderr with structured fields for programmatic handling:

{
  "error": {
    "code": "CONFIG_NOT_FOUND",
    "message": "Config file not found at ~/.config/lore/config.json. Run \"lore init\" first.",
    "suggestion": "Run 'lore init' to set up your GitLab connection.",
    "actions": ["lore init"]
  }
}

Field	Type	Description
code	string	Machine-readable error code (e.g., CONFIG_NOT_FOUND)
message	string	Human-readable error description
suggestion	string?	Recovery guidance (omitted when not applicable)
actions	string[]?	Executable shell commands for recovery (omitted when empty)

Error Actions by Code

Error Code	Actions
CONFIG_NOT_FOUND	["lore init"]
CONFIG_INVALID	["lore init --force"]
GITLAB_AUTH_FAILED	["export GITLAB_TOKEN=glpat-xxx", "lore auth"]
TOKEN_NOT_SET	["export GITLAB_TOKEN=glpat-xxx"]
OLLAMA_UNAVAILABLE	["ollama serve"]
OLLAMA_MODEL_NOT_FOUND	["ollama pull nomic-embed-text"]
DB_LOCKED	["lore ingest --force"]
EMBEDDING_FAILED	["lore embed --retry-failed"]
MIGRATION_FAILED	["lore migrate"]
GITLAB_NETWORK_ERROR	["lore doctor"]

Exit Codes

Code	ErrorCode	Meaning
0	--	Success
1	INTERNAL_ERROR	Unknown/internal error
2	--	Usage error (invalid flags or arguments)
3	CONFIG_INVALID	Config file malformed
4	TOKEN_NOT_SET	GitLab token not configured
5	GITLAB_AUTH_FAILED	Authentication failed
6	GITLAB_NOT_FOUND	Resource not found
7	GITLAB_RATE_LIMITED	Rate limited
8	GITLAB_NETWORK_ERROR	Network/connection error
9	DB_LOCKED	Database locked by another process
10	DB_ERROR	Database error
11	MIGRATION_FAILED	Migration failed
12	IO_ERROR	File I/O error
13	TRANSFORM_ERROR	Data transformation error
14	OLLAMA_UNAVAILABLE	Ollama not running
15	OLLAMA_MODEL_NOT_FOUND	Ollama model not installed
16	EMBEDDING_FAILED	Embedding generation failed
17	NOT_FOUND	Entity does not exist locally
18	AMBIGUOUS	Multiple projects match (use -p)
19	--	Health check failed
20	CONFIG_NOT_FOUND	Config file missing

Field Selection

The --fields flag on issues and mrs list commands controls which fields appear in each item of the response array:

# Preset: ~60% fewer tokens
lore -J issues --fields minimal

# Custom field list
lore -J mrs --fields iid,title,state,draft,target_branch

Presets

Preset	Expands to
minimal	iid, title, state, updated_at_iso

Available Fields

Issues: iid, title, state, author_username, labels, assignees, discussion_count, unresolved_count, created_at_iso, updated_at_iso, web_url, project_path, status_name, status_category, status_color, status_icon_name, status_synced_at_iso

MRs: iid, title, state, author_username, labels, draft, target_branch, source_branch, discussion_count, unresolved_count, created_at_iso, updated_at_iso, web_url, project_path, reviewers

Field selection applies only to list output, not to show (single-entity) output which returns full detail.

Command Response Schemas

Every command in lore robot-docs includes a response_schema field describing the shape of its JSON response. This enables agents to understand response structures without trial-and-error.

# Get schema for a specific command
lore robot-docs | jq '.data.commands.issues.response_schema'

# Get all schemas
lore robot-docs | jq '[.data.commands | to_entries[] | select(.value.response_schema) | {(.key): .value.response_schema}] | add'

Clap Error Handling

Parse errors from the argument parser emit structured JSON to stderr with semantic error codes:

Code	Meaning
UNKNOWN_COMMAND	Unrecognized subcommand (includes fuzzy suggestion)
UNKNOWN_FLAG	Unrecognized command-line flag
MISSING_REQUIRED	Required argument not provided
INVALID_VALUE	Invalid value for argument
TOO_MANY_VALUES	Too many values provided
TOO_FEW_VALUES	Too few values provided
ARGUMENT_CONFLICT	Conflicting arguments
MISSING_COMMAND	No subcommand provided
HELP_REQUESTED	Help or version flag used
PARSE_ERROR	General parse error

Unknown commands include a fuzzy suggestion when a close match exists:

{"error":{"code":"UNKNOWN_COMMAND","message":"...","suggestion":"Did you mean 'lore issues'? Run 'lore robot-docs' for all commands"}}

Agent Self-Discovery

lore robot-docs provides a complete manifest for agent bootstrapping:

lore robot-docs        # Pretty-printed (human-readable)
lore --robot robot-docs  # Compact (for parsing)

The manifest includes:

• All commands with flags, examples, and response schemas
• Deprecated command aliases (e.g., list issues -> issues)
• Exit codes with meanings
• Clap error codes
• Suggested workflows (first setup, daily sync, search, pre-flight)
• Activation methods (flags, env vars, TTY auto-detection)