Skip to main content

​
Your team

Alfred runs five specialists that work on your vault:
SpecialistRoleWhen they work
CuratorReads what you share and creates structured recordsAutomatically on new content
JanitorScans for and repairs structural issuesPeriodic sweeps
DistillerSurfaces deeper knowledge from your recordsOn-demand or scheduled
SurveyorEmbeds records, clusters by meaning, discovers relationshipsOn-demand or scheduled
ClerkStateless LLM worker dispatched for analytical tasksOn-demand by other specialists

​
Checking on your specialists

​
From the dashboard

Go to your Alfred Black dashboard and check the Command Center — it shows the status of each specialist at a glance.

​
Via the API

curl -s /api/v1/workers/status \
  -H "Authorization: Bearer alf_your_key_here"

​
Starting, stopping, and restarting

​
From the dashboard

Use the controls on the Command Center or Services page to start, stop, or restart your specialists.

​
Via the API

curl -X POST /api/v1/workers/up \
  -H "Authorization: Bearer alf_your_key_here"

​
Curator — reads what you share

The Curator watches your inbox and turns raw content into structured vault records.

​
Manual run

If you want the Curator to attend to inbox items immediately: 
curl -X POST /api/v1/workers/process \
  -H "Authorization: Bearer alf_your_key_here"

​
Direct conversation import

Share a conversation directly (bypasses the inbox): 
curl -X POST /api/v1/workers/ingest \
  -H "Authorization: Bearer alf_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"content": "Meeting with Alice about the Q1 launch..."}'

​
Janitor — keeps your vault in order

The Janitor scans your vault for structural problems: broken links between records, missing metadata, and orphaned records with no connections.

​
Run a scan

curl -X POST /api/v1/workers/janitor/scan \
  -H "Authorization: Bearer alf_your_key_here"

​
Repair found issues

After scanning, have the Janitor fix what it found: 
curl -X POST /api/v1/workers/janitor/fix \
  -H "Authorization: Bearer alf_your_key_here"

​
Check Janitor status

curl -s /api/v1/workers/janitor/status \
  -H "Authorization: Bearer alf_your_key_here"

​
View scan history

curl -s /api/v1/workers/janitor/history \
  -H "Authorization: Bearer alf_your_key_here"

​
Ignore specific files

Tell the Janitor to skip certain files during scans: 
curl -X POST /api/v1/workers/janitor/ignore \
  -H "Authorization: Bearer alf_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"path": "note/Personal Notes.md"}'

​
Distiller — surfaces what’s hidden

The Distiller reads your vault and surfaces latent knowledge: assumptions, decisions, constraints, contradictions, and synthesized insights.

​
Run a scan

Identify records that could yield learning records: 
curl -X POST /api/v1/workers/distiller/scan \
  -H "Authorization: Bearer alf_your_key_here"

​
Run extraction

Have the Distiller surface the knowledge: 
curl -X POST /api/v1/workers/distiller/run \
  -H "Authorization: Bearer alf_your_key_here"

​
Check Distiller status

curl -s /api/v1/workers/distiller/status \
  -H "Authorization: Bearer alf_your_key_here"

​
View extraction history

curl -s /api/v1/workers/distiller/history \
  -H "Authorization: Bearer alf_your_key_here"

​
Surveyor — maps your connected world

The Surveyor takes a different approach from the other specialists. Instead of reading individual records, it runs its own four-stage pipeline: Embed (represent records as vectors), Cluster (group records by meaning), Label (name the clusters), and Write (add cluster tags and relationship links back to your vault).
The Surveyor has its own dedicated pipeline and is configured separately via the Surveyor settings in your dashboard.

​
OpenClaw session management

Background workers and Clerk subagents create OpenClaw sessions as they carry out tasks. These sessions accumulate over time and are auto-cleaned — Alfred periodically prunes completed sessions to keep the session list manageable.

​
The alfred-inbox hook

The alfred-inbox hook captures completed OpenClaw chat sessions as stream events. When a session ends, the hook packages the conversation and feeds it into the Event Processor, which classifies it and writes relevant vault records. This means your conversations with Alfred’s agents contribute to your vault automatically — decisions made, tasks discussed, and context shared all become searchable records.

​
Manual cleanup

If you need to clean up sessions manually: 
curl -X POST /api/v1/openclaw/sessions/cleanup \
  -H "Authorization: Bearer alf_your_key_here"

​
Troubleshooting

Inbox not being attended to?
  1. Check the Curator status — is it running?
  2. Try restarting: POST /api/v1/workers/restart
  3. Try a manual run: POST /api/v1/workers/process
Vault has structural issues?
  1. Run a Janitor scan: POST /api/v1/workers/janitor/scan
  2. Then repair: POST /api/v1/workers/janitor/fix
Want to surface deeper knowledge?
  1. Run a Distiller scan: POST /api/v1/workers/distiller/scan
  2. Then run extraction: POST /api/v1/workers/distiller/run

Worker API Reference

Full worker endpoint documentation

Monitoring

Keep an eye on your Alfred