Open chud

Documentation

Workspaces

Containers for a body of work, and exactly what reaches the model from one.

A workspace holds everything about one piece of ongoing work: a name and description, custom instructions, attached files, and a knowledge base that grows as you talk. They are listed at /m/projects and require the Student plan or above.

What actually reaches the model#

When you chat inside a workspace, a context block is assembled and prepended to the system prompt. It contains, in order:

  • The workspace name and description.
  • Your custom instructions for that workspace, verbatim.
  • A list of attached files — name and type only.
  • Up to 30 knowledge entries, sorted by relevance score alone — not by recency. Two entries of equal relevance arrive in whatever order the store returns them, so a newer note is not guaranteed to win over an older one.
  • If the workspace holds more than 30 entries AND a summary has already been built for it, that cached summary is appended as well — in addition to the 30, not instead of them. No summary exists until one is generated, and a workspace with fewer than 5 entries never gets one, so the overflow past 30 can simply be absent from the prompt.

Attached files are listed, not read

The context block passes file names and types so the model knows what exists in the workspace. It does not include their contents. To have a file actually read, attach it to a message — that path sends the document itself.

How the knowledge base grows#

After a reply of at least 80 characters, a separate extraction call pulls out genuinely new facts, decisions and preferences from the exchange and saves up to three of them to that workspace. Casual exchanges with nothing new in them produce nothing. This runs after the answer is already on screen, so it never slows a reply down.

The memory switch does not cover workspace knowledge

Settings, then Memory turns off the personal memory described on the Memory page. It does not govern this: a workspace chat keeps extracting into that workspace's knowledge base regardless. Workspace knowledge is managed inside the workspace itself, and that is the only place to remove it.

Status board and nesting#

  • /m/workspace groups workspaces by build status and lets you advance one with a tap.
  • Workspaces can nest. A workspace with a parent lives inside it and does not appear in the top-level list.
  • A workspace can be shared.

Written from the code that implements it. Verify against src/lib/m/projectContext.js, src/pages/m/Projects.jsx.