v0.33.0

Minor Changes

• Report a bug can now include a screenshot of the app. When you open the Report a bug dialog, OpenKnowledge captures the app exactly as it looked underneath the dialog and shows you a preview inside the compose step. The screenshot is included by default; uncheck it to leave it out. Because the preview shows precisely what will be attached, you can confirm the picture before sending it: a screenshot is an image of your screen and is not redacted the way logs are, so review it and uncheck it if anything on screen shouldn't be shared. When kept, the screenshot rides inside the report bundle at extra/screenshot.png, and like the rest of the bundle it never leaves your machine until you send the report.
• Surface OpenKnowledge's built-in open-knowledge project skill in the Skills UI as a read-only, "Managed by OpenKnowledge" entry. It was previously hidden, so you could not see what your agents actually load. You can now open and read its SKILL.md (and references) from the Skills sidebar and Settings; edit, rename, delete, and install are disabled in the UI, and the skill write/rename/delete APIs refuse mutations to the reserved built-in skills (defense in depth).

Patch Changes

• Report a bug no longer points you to GitHub after you send. The "Thanks for the report!" confirmation used to suggest opening a public GitHub issue and included an "Open GitHub issue" button; both are gone. The dialog still shows your report reference to copy, and if you want to add more it offers writing to support@inkeep.com with that reference.

• Fix "Report a Bug" in the packaged desktop app. Send now attempts to upload your report to the OpenKnowledge team, instead of always opening the "send it by email" draft. The packaged app shipped with no bug-report intake configured, so every Send skipped the upload and fell straight through to email. It now targets the production intake by default (OK_BUG_REPORT_INTAKE_URL still overrides, and unpackaged dev builds are unchanged so a dev run never uploads by accident). If the upload cannot be completed, Send still offers the same email draft, so no report is lost.

• Fix the Mermaid slash command inserting an invisible, zero-height block. Selecting Mermaid from the / menu previously dropped a near-zero-height sliver: nothing appeared to happen, repeated inserts stacked invisibly, and the hover toolbar (edit / delete) was clipped. An empty Mermaid block now renders a clear "Add a Mermaid diagram" placeholder card and opens the diagram source editor on insert, so there is always a visible, adequately-sized target to author or remove.

• Stop OpenKnowledge's built-in open-knowledge project skill from causing recurring git sync conflicts. The app regenerates that skill into each editor's host dir (.claude/skills/open-knowledge/, .cursor/…, .codex/…, .github/…, .opencode/…, .pi/…) on every open, and different app builds stamp a different version into it — so when it was committed, teammates on different builds collided under git auto-sync (merge conflicts, or a repeatedly "paused, external changes pending" sync).

  It is now treated as a local, per-machine artifact. On ok init and on project open, OpenKnowledge writes a committed .gitignore entry that always excludes this projection (in both shared and local-only sharing modes, and it travels to every clone so a fresh checkout is protected before the app ever runs). Nothing is lost, since the app regenerates the file on each open. For repos where the skill was already committed, opening the project untracks it automatically via a dedicated, conflict-safe commit; teammates will see it removed on their next pull. Authored skills you place under .{editor}/skills/<your-name>/ are unaffected and continue to follow your OpenKnowledge sharing setting.

• Show a read-only Properties panel when viewing a read-only skill file's markdown (for example the built-in open-knowledge skill's SKILL.md). Previously the frontmatter was stripped and hidden in the read-only viewer, so a managed skill's name, description, and other metadata were invisible; the editable skill panel already showed them. The read-only viewer now renders the same "Properties" section above the body, in read-only mode.