alecs5am/ralphy/troubleshooting

Troubleshooting playbook

Read this when: "set up", "set up keys", "ralphy doctor", "nothing works", "read logs", "debug failed generation", "missing key", any ralphy CLI usage question.

Plumbing role. Other roles call me when something breaks, when the environment isn't up, or when the user wants to inspect under the hood. Ops + CLI expert layer beneath the creative roles.

STOP rule. Every observability question is a ralphy verb. Don't cat / tail JSONL by hand — the log readers below sort, merge, and filter for you. AGENTS invariant #2.

CLI cookbook

Every observability question is a `ralphy` verb. Don't `cat` JSONL by hand — the log readers below sort, merge, and filter for you.

# Env / setup health
ralphy doctor                                                # full env check (keys, deps, project)
ralphy doctor -p                                             # human-readable
ralphy status                                                # capabilities + linked project
ralphy setup                                                 # interactive wizard (first-time keys)
ralphy config get / set                                      # config CRUD
 
# Logs (per-project, append-only via cli/lib/gen-log.ts)
ralphy project log <id> --type generations --limit 50        # latest model calls + cost + errors
ralphy project log <id> --type user-prompts --limit 20       # what the user said, when
ralphy project log <id> --type user-assets --limit 20        # what the user uploaded
ralphy project log <id> --type all --limit 200               # merged, chronological JSON
ralphy project timeline <id>                                 # pretty chronological log (table)
 
# Workspace inspection
ralphy workspace stats                                       # cross-project counts + disk usage
ralphy project list -p                                       # status per project
ralphy assets list                                           # ralphy-assets companion repo
ralphy assets cache-info                                     # local SHA-verified cache
ralphy assets pull <template>                                # auto-runs on `template use`
 
# Render-specific debug
ralphy project show <id> --assets                            # what's on disk
ralphy project show <id> --scenario                          # current scenario.json

If the user asks "why did this generation fail" — ralphy project log <id> --type generations | jq '. | select(.status=="error")' is the fast move. Don't grep JSONL by hand.

Sub-docs (read on demand)

Sub-tasks

What I read on start

• `AGENTS.md` — invariants (chat is the interface; no auto-launched UI or scheduler).
• pwd + package.json + CLAUDE.md + MODELS.md to confirm repo root.
• docs/agent-guide.md — canonical CLI reference. I don't memorize commands; I look them up.
• docs/cli-spec.md — flag-level spec.

Hard rules (inherited from AGENTS.md)

1. NO auto-launch. I don't run a UI or scheduler in the background. Chat is the interface. See core/doctor.md.
2. Connector-owned keys only. ralphy doctor reports required and optional connectors; keys never leak outside their registered provider modules.
3. No provider MCP setup. Provider access goes through Ralphy connectors, not ad-hoc MCP servers.
4. Logs append-only. cli/lib/gen-log.ts enforces the format. See core/troubleshooting.md.

Background processes — manners

• I don't spawn long-running processes. AGENTS invariant.
• If the user explicitly asks for preview — I'll say to run bunx hyperframes preview .ralphy/workspaces/<ws>/projects/<id> foreground in a separate window.
• If the user complains "port busy" — show lsof -iTCP:<port>, user decides whether to kill / leave it.

Handoff

• After env up + CLI clear → hand back to the role that triggered me (usually producer playbook).
• Fresh-machine after setup → producer playbook for the first real end-to-end task.
• HyperFrames-specific → [hyperframes playbook](../hyperframes/references/playbook.md) (not me).