# Organize context

## Choose the right format

| Content | Store as | Example |
|---|---|---|
| Reusable workflow | Skill | How an agent performs a code review. |
| Short durable information | Memory fact | A project decision or preference. |
| Connected knowledge | Wiki | Linked articles and attachments. |
| General requirements | Instructions | Rules for your work. |

## Find before adding

Search [Memory](/account/memory) for facts and [Context objects](/account/objects?kind=knowledge) for wiki articles. For full-text search within one wiki, open it under [Wikis](/account/wikis). Connected clients can search and retrieve content over MCP. Wiki articles load on demand instead of filling the context window at connection time.

## How we test context quality

Our MCP acceptance tests check whether a client reads the right sources, uses current knowledge and respects sharing permissions. A plausible answer alone does not pass. [Scenarios and how to read the results](/docs/sdk/testing#core-context-acceptance). Repeated evaluations distinguish passing, failed and incomplete scenarios and compare quality alongside latency, tokens and cost. These tests use synthetic data and do not guarantee every model or client behaves identically.

## Keep provenance

Give project-specific facts their project origin. This preserves context without restricting recall of lessons from other projects.

## Review versions

Context objects have draft and stable versions. Review a draft before promoting it. Facts have their own memory and correction workflow. See the [MCP reference](/docs/reference) for tools.

## Workspaces are personal views

A [workspace](/account/workspaces) selects context objects for a connection. It grants no access. Use [sharing](/docs/sharing) to make content available to someone else. On [Context objects](/account/objects) you can narrow the list to one workspace; the type bar above it shows how your used storage splits across object types and filters by type in one click. Each row names the object's workspaces; in the reader, one click on a workspace chip adds the object to it or takes it out.

## Shared selection in plugins and wikis

Every plugin view uses the same workspace selection, including Context explorer, Wiki and custom plugins. It lists your personal workspaces. **All workspaces** shows the content of every workspace together; an empty workspace does not fall back to unrelated content.

Assign content under [Workspaces](/account/workspaces). Assigning a whole wiki or a plugin's content also includes future content, subject to current access rights. The selection survives navigation, search and downloads. Save unfinished changes before switching: a different workspace closes the previous editors. Returning to a browser tab refreshes only the workspace choices and preserves form input.

You manage two things: workspaces and buckets. A workspace says where content lives and where an agent works; a bucket says who else may use it. A workspace grants no access and widens no agent or MCP credentials.

A bucket has a title and an optional description. Members can read both; only the owner can edit them. Over MCP, set them with `create_bucket` and change them with `configure_bucket`.

Bucket members can add their own objects to a bucket. The bucket owner chooses whether members can normally only read shared objects, propose changes for approval, or edit directly. Object owners can allow editing on individual objects even when the bucket defaults to read-only. Editing another owner's object under a bucket-wide setting requires that owner's consent, and they can further restrict the access. Changes awaiting approval appear in the object owners' action items; the published version stays unchanged until approval. For MCP updates, `parent_version_id` names the version the change is based on.

Choose **Use bucket rule** to remove an object's individual rule. It then follows the bucket rule, including later changes. Your own objects already follow that rule until you set an individual one; the interface shows the current access. For another owner's object, adopting the bucket rule also requires that owner's explicit consent. An individual **Read only** rule, by contrast, remains in force if the bucket later allows editing. Over MCP, the object owner calls `configure_bucket` with `bucket_id`, `object_id`, and `object_write_consent: "inherit"`.
