brainattic.ai

Release notes

Version 4.4.0 brainattic is a shared knowledge base for teams and their AI agents, hosted at app.brainattic.ai by Finite Software Systems Ltd. This plugin connects ChatGPT to the same workspace-scoped content over MCP, now through 79 tools (53 in 3.1.0). What changed since 3.1.0 - 4.0.0: files can be attached to documents directly: kb_attachments_begin_upload (one-use, five-minute upload capability) and kb_attachments_import (a file shared in chat, through ChatGPT file parameters). - 4.1.0: kb_attachments_view_image shows an existing image attachment. - 4.2.0: that image is rendered in the ui://brainattic/image-viewer-v1 component, which loads resources only from https://app.brainattic.ai. - 4.3.0: Skills, 22 kb_skills_* tools to list, read, search and author reusable team instructions with revision history. brainattic stores Skill files and never executes them. - 4.4.0: kb_attachments_import_url attaches a file from a public HTTPS URL. It requires an independent SHA-256 and refuses private and internal addresses. Annotations Every tool sets readOnlyHint, destructiveHint and openWorldHint explicitly as booleans: 28 read-only, 17 destructive, 4 open-world (kb_attachments_import, kb_attachments_import_url, kb_reminders_create, kb_reminders_create_schedule). kb_documents_edit_apply, kb_skills_edit_apply, kb_skills_edit_put_file and kb_skills_edit_remove_file are non-destructive because they change only the caller's open edit-session draft: nothing is published until the matching *_edit_commit, earlier revisions stay retained, and *_edit_discard drops the draft. Response data and the Privacy Policy Reviewers will read Privacy Policy version 2026-10-11 at https://brainattic.ai/privacy (published 2026-10-12, effective 2026-10-26). Every response path the connector can emit (291, including nested and error payloads) is assigned a category, and an automated test fails the build if any path is uncategorised. Each category is named in §4: - record identifiers of the objects you work with (document, revision, attachment, edit-session, reminder, schedule and Skill identifiers); - names, slugs, links, file paths, revision numbers and shortened snippets that locate content; - last-modified, archival, due, expiry, schedule, revision, purge and delivery timestamps; - file metadata (name or path, type, byte size) for attachments and Skill files, and SHA-256 digests in Skill file descriptors; - relevance signals for search results (relative score, matching channel, confidence); - counts and sizes; the state of an object after a call; rule-linked Skill recommendations; fixed warnings about untrusted procedural content; - project and group display preferences; short-lived download or upload links only when the client asks; - error reference codes and the field, tool or permission a refusal names, and for a policy refusal the acceptance link and policy versions. The content the user asks for (document bodies, passages, revisions, rule documents, attachment files, Skill instructions and files) is Customer Content under §4. §4 also discloses the MCP access event recorded for each call that touches the knowledge base, and the document-search log. §10 states their retention (90 days by default). No response field carries an email address, a personal name or a user account identifier. Names in responses are the names of workspaces, projects, groups, Skills and files. Temporary file download URLs, provider file IDs and source URLs are used only to fetch the bytes and are not retained or returned.

Declared in the saved package. Remote tools may change independently.