Summary
If the memory_dir for an agent (or top level) is unwritable (eg: bad permissions), aura only finds this out at runtime, and continues attempting to work, even when work is now impossible.
Aura should check/create all memory_dir values at start-up, and exit with an error if they are unusable.
Reproduction
Configure a memory_dir that points to a directory that aura cannot write to (eg: memory_dir = "/root/foo"). Launch aura. Attempt an action that would require using the dir (eg: a tool that requires HITL).
Relevant log output
aura-1 | 2026-07-30T17:48:38.895Z INFO aura::orchestration::orchestrator: Orchestrator: Initializing execution persistence at: /root/aura-orchestration
aura-1 | 2026-07-30T17:48:38.896Z ERROR aura_web_server::streaming::handlers: Stream error: Failed to initialize persistence: Permission denied (os error 13)
aura-1 | 2026-07-30T17:48:38.896Z INFO rmcp::service: task cancelled
aura-1 | 2026-07-30T17:48:38.896Z DEBUG rmcp::transport::streamable_http_client: cancelled
aura-1 | 2026-07-30T17:48:38.896Z DEBUG aura_web_server::streaming::handlers: Stream processing completed with StreamError("Failed to initialize persistence: Permission denied (os error 13)")
aura-1 | 2026-07-30T17:48:38.896Z WARN aura_web_server::handlers: Stream producer ended with error: Failed to initialize persistence: Permission denied (os error 13)
aura-1 | 2026-07-30T17:48:38.896Z DEBUG rmcp::transport::worker: worker quit with reason: CancelledAdditional Context
The error is presented to the user as something that isn't helpful, and is misleading. In the below case, HITL is configured for the tool call being attempted:
Question: how many pipelines exist in my account
Answer: The upstream model provider (openai/gpt-5.4-nano) returned an error and the request could not be completed. Please try again or contact support if the issue persists.
Tools: []
Upload screenshots
No response
Searched Issues
Code of Conduct
Summary
If the
memory_dirfor an agent (or top level) is unwritable (eg: bad permissions), aura only finds this out at runtime, and continues attempting to work, even when work is now impossible.Aura should check/create all
memory_dirvalues at start-up, and exit with an error if they are unusable.Reproduction
Configure a
memory_dirthat points to a directory that aura cannot write to (eg:memory_dir = "/root/foo"). Launch aura. Attempt an action that would require using the dir (eg: a tool that requires HITL).Relevant log output
Additional Context
The error is presented to the user as something that isn't helpful, and is misleading. In the below case, HITL is configured for the tool call being attempted:
Upload screenshots
No response
Searched Issues
Code of Conduct