WeKnora: grounded answers, scoped memory and deliberate operations
WeKnora operations: workspace permissions, personal memory and sandbox authority
Distinguish knowledge access from personalization and skill selection from execution isolation, network policy and credential exposure.
What you will learn
- Personalization does not grant document access
- A skill catalog entry is not a ready execution environment
- Review networking, rollout and secrets together
Before you start
- Basic HTTP and container concepts
- Understanding of documents, passages and model providers
Separate ingestion, retrieval, answer support and memory scope, then design an evidence-based acceptance exercise.
Key takeaways
- Memory use, deletion and document authorization are separate.
- Catalog storage, installation and agent selection have distinct states.
- A working directory is not a sandbox security boundary.
Personalization does not grant document access
The memory guide scopes data by workspace and caller identity. Workspace, personal and agent/request switches jointly constrain use; inferred pending items do not enter prompts until confirmed. Memory can shape interpretation and ranking without extending knowledge-base permissions.
Disabling personal memory pauses use; it is not the same operation as deleting stored data. Review export, deletion and retention deliberately. A source-supported preference is still personal information, so avoid importing real profiles into a demonstration or claiming that turning off a feature erased its history.
A skill catalog entry is not a ready execution environment
The sandbox guide separates storing a package in the catalog, installing it into a backend snapshot and selecting it for an agent. Mentioning a skill does not revoke access to other already authorized skills. Installation-ready state also does not prove that arbitrary scripts are harmless.
Docker execution is opt-in; mounting the host Docker socket grants substantial host-control authority. The removed local host-process backend must not be presented as a current option. The guide says scripts default to root inside the sandbox and that /workspace is a convention, not a filesystem jail for root commands.
Review networking, rollout and secrets together
Cube/E2B network policies differ from Docker network modes. Existing instances do not automatically receive changed policy; verify newly created or rebuilt instances. Skill rollout can rebuild a session on its next turn and lose transient state, so collect deliverable files through the documented output path.
Personal and workspace variables follow distinct precedence rules. Disabling a skill does not delete personal credentials, and an environment secret may be readable by scripts given that environment. Begin with synthetic inputs, limited egress and minimal credentials; no sandbox, socket mount or external skill installation was performed here.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Verify the caller and knowledge scope.
- 2
Review memory consent and lifecycle.
- 3
Audit execution backend and actual network policy.
- 4
Collect artifacts before a planned sandbox rebuild.
Copy-ready example
{
"operationsWorksheet": true,
"documentScopeChecked": false,
"memoryConsentChecked": false,
"catalogSaved": null,
"sandboxInstallReady": null,
"networkPolicyVerified": false,
"dockerSocketMounted": false,
"realSecretsUsed": false
}Frequently asked questions
Does mentioning one skill disable every other skill?
No. The guide explicitly says other already authorized skills remain available.
Does /workspace restrict root to that directory?
No. It is the working-directory convention, not a root filesystem jail.
Sources
- WeKnora / website-docs/03-features/23-memory.mdSource checked 2026-09-14
- WeKnora / website-docs/03-features/22-skills-sandbox.mdSource checked 2026-09-14
- WeKnora / website-docs/01-getting-started/03-quickstart.mdSource checked 2026-09-14