OpenKnowledge Files

Minor Changes

• Files, folders, and images now ride ACP prompts. The agent-thread composer accepts three attachment paths — @ picks workspace files and folders from the shared mention menu, the + button opens the OS file picker, and files dropped anywhere on the chat panel attach the same way. Non-image files stay workspace-scoped (matching Zed's behavior: the agent's tools can only reach files inside your project), so anything dropped from outside gets refused up front with a clear message. Images drop or paste from anywhere in the OS and preview as thumbnails above the input, with per-file type + size validation and a remove control.

On send, chips become native ACP parts alongside the text — EmbeddedResource with the file's text contents when the agent advertised promptCapabilities.embeddedContext, ResourceLink (with a file:// URI + name + mime) otherwise; folders always as a directory reference; images as ImageContent when the agent advertised promptCapabilities.image. Agents that didn't advertise image support get a "doesn't accept images" refusal on the drop. Sent messages replay their attachments as chips in the transcript so a reloaded thread shows exactly what was handed to the agent.

Patch Changes

• Team-shareable .ok artifacts now auto-sync in shared projects. The project config.yml, the seeded .ok/.gitignore, frontmatter lint schemas (.ok/schemas/*.json), note templates (project-level and folder-level), and folder metadata (<folder>/.ok/frontmatter.yml) are staged and pushed by the auto-save cycle, and deleting them propagates too. Previously a teammate could author a schema and sync would run green without it ever reaching anyone else. Machine-local state (.ok/local/, .ok/worktrees/, legacy root state files) and secret-suffixed files are never synced, local-only projects behave exactly as before, and these files still do not appear in the sidebar or document index. A merge conflict on .ok/config.yml still auto-resolves to the remote version, overwriting local config edits, but the server log now records a warning so the overwrite leaves a findable trace (there is no in-app notification for it yet). Projects with content.dir set to a subfolder now sync the project-root .ok set as well.

Linkable files inside the configured attachment folder now auto-sync without requiring a Markdown document inside that folder. Unconfigured asset directories remain outside the sync scope.

• Frontmatter schemas are now presented as a stable feature throughout the app and documentation.

Downloads