Skip to main content
​
Groups and continuous updates

​
Groups

Managing access one member at a time does not scale. Groups are named collections of workspace members, created and managed in Settings, that can be granted access to a file or folder in one step from the access picker. Owners and admins can create, rename, and delete groups, and change a group’s members. Learn more.

​
Continuous updates (Early access)

A new HubSpot email from John Doe with the subject I'm leaving ACME triggers an update to the ACME Inc. file, replacing the line naming John Doe as internal champion with one noting he left in September 2025 and that Jane Smith is now the championA repository kept up to date by hand is outdated the moment the work stops. With continuous updates, every record a sync brings in triggers an agent that reads the repository and the relevant structure files, decides what to create, update, or leave alone, and records the result as a change. Continuous updates are in early access; contact support@qontext.ai to enable them for a workspace. Learn more.
  • Editor: Formatting is kept when pasting Markdown into a file.
  • Editor: The raw Markdown editing mode is now available when creating files, not only when editing existing ones.
​
Context agents can ask questions, and live updates

​
Context agents can ask questions

A context agent no longer has to guess when a request is ambiguous. It can pause and ask a multiple-choice question, shown as option cards in the chat, then continue once an option is picked or a different answer is typed. Learn more.

​
Live updates

The file tree and any open file now update as changes land, whether they come from a context agent, a sync, or another browser tab. File content refreshes in near real time, and the tree reflects additions, removals, and renames without a reload. Learn more.
  • File tree: Files can now be created at the root of the repository, not only inside a folder.
  • API keys: An API key can be rotated in place, replacing its secret without rebuilding its access configuration.
  • Member invites: Invite links to the workspace can now be copied from the members table for direct sharing.
​
Salesforce connector

​
Salesforce connector

Salesforce is now a supported data source. Connect a Salesforce org to sync its records into a context repository. Qontext only reads data, and access stays bounded by the connected user’s own Salesforce permissions. Learn more.
  • Google Drive: Google Drive now syncs PDF and Office files (pdf, docx, xlsx, pptx), selectable in the Filters tab.
  • Sources: A Sync latest data action pulls the most recent data from a source on demand.
  • Editor: Internal links pointing to a file that no longer exists are now flagged in the editor.
  • Changes: A commit with no file changes now shows an empty state instead of a blank panel.
​
Context agents, SharePoint, and structure files

​
Context agents

Context tab chat where a prompt asks the agent to summarize connected Notion and Slack sources into a new file, and the agent replies that it created customer-onboarding.md in Product/ProjectsTurning scattered notes and source data into well-organized context is manual work. Context agents do it from a chat on the Context tab: describe what is needed and the agent builds folder structures, writes and edits files, and draws on connected sources, with every change versioned and shown in the Changes tab. Learn more.

​
Structure files

A self-maintaining repository is only useful if it stays organized. A structure file tells Qontext how a folder is organized, what belongs in it, how files are named, and how careful automatic updates must be, so new content lands where the team expects it. Learn more.

​
SharePoint connector

SharePoint is now a supported data source. Connect SharePoint sites to sync documents, site pages, and lists into a context repository, with SharePoint’s own permissions always respected. Filters and incremental sync work the same as the other connectors. Learn more.
  • MCP clients: The list of connected MCP clients now shows every client, not only those authorized in the last 7 days.
​
Edit files as raw Markdown

​
Raw Markdown editor

The rich editor is the fastest way to write, but sometimes it helps to work with the Markdown directly. A new toggle in the editor top bar switches any editable file to a raw Markdown view, frontmatter included, and back again. Learn more.
  • Cross-references: Links between files are now stored by file, so they keep working when the target is renamed or moved. File and folder names are validated on create and rename, and saving a file that links to a missing file now shows a clear error.
  • Diff view: A file created with no content now shows an empty-file state in the Changes diff instead of a blank panel.
  • Settings panel: The file settings panel now closes when clicking into the editor.
​
Review changes before they take effect

​
Change reviews

Change reviews screen showing a list of open changes from Notion, HubSpot, and Confluence with accept and reject controls, next to a summary and diff of the selected changeA context repository is written to from many directions: members editing files, connectors syncing data sources, and agents writing through the API and MCP server. Change reviews bring every pending change together on a new Changes screen, where each one can be compared against the current file and approved or rejected before it takes effect. Changes that do not conflict are reconciled automatically, so review is reserved for the edits that need a decision. Learn more.

​
Protected files

Some files should never change without a second look. Turning on Require review in a file’s settings protects it, so every change is sent for review before it merges, no matter where the change came from. Learn more.
  • Changes: A count badge on the Changes item in the sidebar shows how many changes are waiting for review.
  • Changes: Saving a file that needs review shows a banner linking to the pending change, and protected files are marked with a lock icon.
  • Saving files: A reason for a change is now optional when saving.
  • Editor: Version history and retrieval logs moved to a new full-width top bar, giving the editor more room.
  • File tree: Folders can be renamed and moved directly in the file tree.
  • File tree: Folders can be created at the root of the shared context tree.
  • Retrieval: Hybrid search returns better results for conversational queries.
  • Retrieval: Responses from the /v1/retrieval endpoint are ~80% faster.
​
Access management for files and folders

​
Access controls on files and folders

Access controls panel showing per-file and per-folder access levels for members and API keysAccess to the files and folders in a context repository can now be restricted for both workspace members and the agents connecting to it, all from the Context screen. Permissions can be granted across the whole workspace, on a folder and all its descendants, or on a specific file. Access levels run from No access through Can read and Can edit to Full access, perfect to mirror how teams are actually organized. Learn more.

​
Improved API key access controls

Newly created API keys can either inherit the access of the member who created them or be managed independently. Alongside the access set on an individual file or folder, the files and folders an independently managed key can access are also managed from a new Access Controls tab in the API key settings. Learn more.
  • Self-update: qontext update updates the CLI in place to the latest release.
  • Version notice: The CLI now warns once a day when a newer version is available.
​
Version history for files

​
File version history

File version history panel listing each version and its sourceEvery file in a context repository now keeps a version history, shown in the file sidebar. Each version lists its source, so connectors like Slack or Notion are named directly, while manual, MCP, and API-key updates appear as a workspace member. Learn more.
​
MCP server supports API-key auth

​
MCP server access with API keys

The Qontext MCP server now accepts API keys in addition to OAuth. Clients connect by sending an X-API-Key header, and all MCP tools work for API-key callers. Learn more.
  • MCP client usage logs: MCP client details now include a Usage Logs tab showing past retrievals.
  • Member file deletion: Workspace members can now delete any file in the workspace, not only files they created.
  • Editor blank lines: The editor no longer shows blank lines as empty paragraphs.
  • Delete errors: Deleting a file or folder without permission now shows a clear message instead of a generic error.
  • Longer sessions: MCP sessions stay connected instead of expiring after a few minutes.
  • Multiple workspaces: Fixed MCP tool calls failing for users who belong to more than one workspace.
​
Create and delete folders in the UI

​
File and folder management

Folders can now be created and deleted directly in the file tree, including from its empty state. Files can be renamed, removed, moved, and dragged between folders. Learn more.

​
Website source filters

Website data sources now show the Single Page and Deep Crawl options in their Filters tab, matching the other connectors. Learn more.
  • Unsaved changes guard: Leaving a file with unsaved edits now prompts before discarding, and drafts are kept so they survive a refresh.
  • File paths in usage logs: API key usage logs now show file names, with the full path on hover.
  • Saving files: Saving a file no longer removes blank lines.
​
Create files in the UI

​
Create and edit files

Files can now be created directly from the file tree. The editor adds a slash command for inserting tables, headings, lists, and code, and links to other files can be added by searching for them inline. Learn more.

​
Website source details

Website data sources now have a Details page, and any source can be enabled or disabled from it. Learn more.
  • API key usage logs: API keys now have a Usage Logs tab showing how each key has been used.
  • Loading states: Smoother loading and empty states for the file tree and data sources.
  • Legacy tabs removed: The legacy Vaults and Credentials tabs were removed.
​
Safe concurrent writes

​
Safe concurrent edits

Writes to a context repository now go through a merge queue. When two changes to the same file happen at once, they merge automatically if they do not overlap, and are flagged for review if they do, so simultaneous writes can no longer corrupt a contextbase.

​
Inline source filters

The Filters tab on each data source now has a working editor for Google Drive, HubSpot, Notion, Slack, and Confluence sources.
  • Visual polish: New file and folder icons, and more consistent page spacing.
  • hybrid_search tool: New tool for retrieving context from a workspace.
​
Edit files in the UI

​
Edit files in the UI

Editing a markdown file in the file editorThe file viewer is now a full editor. Files open in a markdown editor with a formatting toolbar and inline title editing, a message can be added when saving, and files can be deleted from the file detail page. Learn more.

​
Sync history for data sources

The Syncs tab on a data source now shows a filterable history of past sync runs.
  • qontext_mv: New tool to rename or move files.
  • qontext_grep: New tool to search file contents.
​
Markdown rendering fixes

​
Markdown rendering

The file viewer now displays document frontmatter as a table instead of raw text, and renders Markdown tables properly.
​
Qontext v1: context repositories

​
Context repositories

Qontext context repository with the file tree and a document openQontext v1 introduces context repositories, a file-based view of all context in a workspace. A file tree and document viewer make it possible to browse and read every file, and the Context page is now the default view. Learn more.

​
Per-file retrieval logs

Every file has a retrieval history showing when it was accessed and which MCP client or API key requested it. Learn more.

​
API keys and MCP clients

API keys and MCP clients can now be managed from dedicated workspace pages, including creating and revoking keys and connecting MCP clients, with status and usage logs in one place.

​
Workspace settings and user invites

Workspaces now have a dedicated settings area for managing the workspace name, URL, and members. Collaborators can be invited by email and assigned a role, and pending invitations can be revoked before they are accepted. Learn more.

​
Workspace skills

Skills folder in a context repository file treeSkills can be installed and synced into a workspace through a CLI with a web-based approval flow. Learn more.
  • Permission-aware controls: Actions a user cannot perform are now disabled with a tooltip explaining why, and permission errors show a clear message instead of a generic failure.
  • File operations: New qontext_mkdir, qontext_write, and qontext_rm tools let agents create folders, write files, and delete files.
  • qontext_find: New tool to search for files.
  • Skills CLI: New CLI to install and sync workspace skills.