tinyhumansai/openhuman · error
memory directory missing: {}
Error message
memory directory missing: {} What it means
Doctor workspace check: the <workspace>/memory directory does not exist. The memory store expects this folder for its persisted data; the check is a warn (not error) because the directory is created lazily on first write, but its absence on a long-lived install suggests the workspace was wiped, moved, or never initialised.
Source
Thrown at src/openhuman/platform/doctor/core.rs:441
}
}
Err(e) => {
items.push(DiagnosticItem::error(
cat,
format!("directory is not writable: {e}"),
));
}
}
// Minimal workspace folders
let mem_dir = ws.join("memory");
if mem_dir.exists() {
items.push(DiagnosticItem::ok(
cat,
format!("memory directory: {}", mem_dir.display()),
));
} else {
items.push(DiagnosticItem::warn(
cat,
format!("memory directory missing: {}", mem_dir.display()),
));
}
// Check for config templates or docs
let prompt = ws.join("SYSTEM.md");
if prompt.exists() {
items.push(DiagnosticItem::ok(
cat,
format!("SYSTEM prompt: {}", prompt.display()),
));
} else {
items.push(DiagnosticItem::warn(
cat,
format!("SYSTEM prompt missing: {}", prompt.display()),
));
}View on GitHub (pinned to 7491200858)
Solutions
- Run one memory-ingesting action (a chat turn or memory sync) and let the core create it
- Verify workspace_dir in config points at the intended workspace root if the path looks wrong
- If the workspace was moved, migrate or repoint config rather than expecting the old memory tree to reappear
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/platform/doctor/core.rs:441 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/1128bd6e2f63e414.
Report an issue: GitHub.