Skip to main content

​
Synopsis

urchin doctor
No flags.

​
Output

doctor prints the resolved configuration and current journal state to stdout. Example: 
urchin — local memory sync substrate

identity
  account:      samhc
  device:       saucemachine

config
  source:       ~/.config/urchin/config.toml
  vault_root:   /home/samhc/brain
  journal_path: /home/samhc/.local/share/urchin/journal/events.jsonl
  intake_port:  18799
  cloud_url:    https://www.orinadus.com/api/urchin-sync
  cloud_token:  [set]
  intake_token: [not set]

journal
  exists:       true
  events:       1042
  file_size:    412 KB
  last_event:   2026-05-04T20:00:00Z (source: claude)

​
What it checks

SectionWhat is shown
identityResolved account and device from env, config, or system defaults
config.sourceWhether config was loaded from the file or defaults
vault_rootPath to the ~/brain vault
journal_pathFull path to events.jsonl
intake_portPort the HTTP server will bind
cloud_url / cloud_tokenWhether cloud sync is configured ([set] or [not set])
intake_tokenWhether HTTP auth is enabled
journal.existsWhether the journal file is present
journal.eventsCurrent event count
journal.last_eventTimestamp and source of the most recent event

​
Use cases

  • Confirm that env var overrides are being picked up correctly.
  • Verify the journal path before running collectors or the serve daemon.
  • Check that cloud_token is set before running urchin sync.