Overview
Your library and local processing at a glance.
System status
Devices
Needs attention
—Current work
Recent activity
Ask your knowledge
Answers grounded in your local knowledge.
Knowledge conversation
Local onlyWhat would you like to know?
Ask a question about your indexed documents. Sources appear alongside the answer.
RAG Audit
RAG processing and agent interactions with NAS knowledge.
| Date & time | Agent | Action | Reason / purpose | Outcome | Channel / trigger | Component |
|---|---|---|---|---|---|---|
| No entries loaded. | ||||||
Agent Diary
Daily actions across all OpenClaw agents and channels.
| Date & time | Agent | Action | Reason / purpose | Outcome | Channel / trigger | Component |
|---|---|---|---|---|---|---|
| No entries loaded. | ||||||
Documents
Browse your library and manage how knowledge is used.
Immediate folders and files from the catalogue. Source folders and filenames stay unchanged.
Cloud and indexing permissions
Cloud allowed permits cloud use; folder permissions cover existing and future descendants. File permissions apply to the current revision. Catalogue only stops content processing and retrieval while keeping the file in the catalogue. These controls are independent; unchecking Catalogue only restores normal indexing rules.
| Name | Content state | Type | Modified | Cloud allowed | Catalogue only |
|---|
Processing
Follow local work and resolve items that need a decision.
How recovery and review work
Retry processing starts a new chain with the selected local model and starting context. Recoverable failures try supported contexts on the primary model, then one alternative, with at most six attempts. Context never exceeds 64K; unavailable devices or models wait without using attempts. Source problems go to human review. Ignore issue dismisses this failed attempt and keeps its history. Catalogue only keeps the original file and catalogue entry, disables content processing and retrieval, and clears its issues. Catalogue only requires the policy password and does not change cloud permission.
Indexing approval
Admission rules
How hardware admission works
CPU, GPU and memory readings from TotoroAI and Strix. Missing sensors show —. Refreshes every five seconds while this tab is open. The server manages telemetry and task admission; pausing admission waits to start new work and does not cancel a running task.
Eco favors other apps. Normal balances RAG with other work. Full can use the environment ceiling when headroom allows. Priorities apply to new requests across RAG tasks; they do not reserve hardware or interrupt running work.
Settings
Appearance, policy editing and effective runtime configuration.
Appearance
Choose the application theme. Saved in this browser.
Policy editing
Browsing is available. Unlock to change cloud access or catalogue-only policies.
Effective runtime
Current runtime configuration for this local workspace. Read only.
Watched source summary
Manage workload priorities
Adjust device priorities and effective processing workload.