meinKontextDocs
Navigation & search

Updates

Changelog

What has changed for you in meinKontext.

What has changed in meinKontext, newest first: what you notice in the product and the fundamentals behind it as far as they concern you. What comes next is on the roadmap.

17 November 2026

  • When an access preview for an agent cannot be done as asked, the answer now says what to change instead of pointing to plugin actions.
  • An agent's wiki access no longer offers write levels the platform refuses; it points to the wiki's roles instead.
  • Granting an agent access to a context object on the agents page works again; it failed every time.
  • Revoking an agent's access over MCP now revokes exactly the credential you name, and revokes a whole agent only when you ask for that explicitly.
  • Platform admins now see failed background jobs in the admin area, can delete them or run them again with a reason, and get each waiting one as an open item.
  • Platform admins see on the platform page how many accounts and organizations were created per day and how many addresses are verified, list every invite code with its seats, create and disable codes and set a person's invite allowance there, without a terminal.
  • Meetings can be found by their calendar event: agents can ask for the meetings that belong to one event.
  • A plugin you build yourself can mark a step as an approval: only you take it, in the browser, and no connected AI client or agent can take it for you.
  • A search limited to one wiki now says clearly when that wiki is not available to you, instead of returning an empty result.
  • Feedback can now carry screenshots and other files: attach them when you report a problem or reply, and the support team sees them next to your message. Deleting your account removes the files too.
  • Every feedback report you send now belongs to one of your workspaces: the workspace your connection uses, otherwise your Standard workspace. Deleting a workspace keeps your reports in your Standard workspace.
  • New feedback reports now appear among the open items of the support team, and a question to you about your own report appears among your open items until you answer it.
  • An agent now receives its instructions and the skills you shared with it as soon as it connects, through the standard skills interface of MCP clients, without any meinKontext-specific call.
  • Sharing a single calendar through a bucket no longer locks its owner out of their calendar after the latest update; such a share pauses until it can be offered again.
  • Meetings now reads Markdown files from Jamie, Google Meet notes documents and Wispr Flow exports with their speakers and times instead of as plain paragraphs. The import suggests the matching converter for a file and you confirm it.
  • A file's summary is imported as its own source, and every source now shows whether it is a transcript, a summary or notes.
  • The calendar update that could not be applied to existing installations now applies, with every existing share kept as it is.
  • If a plugin update ever cannot be applied, the page now says what happened, that the operator has been notified and what keeps working.

16 November 2026

  • Platform admins get a capacity page with graphs of how many copies of each service ran, how busy processors, memory, the database and the queues were, for the development and the production environment over the last hour up to the last seven days.
  • The admin area now also shows which version each part of meinKontext is running, whether maintenance is switched on and why, and when new versions were rolled out.
  • Plugins built in the Studio can now let your agents run single steps of a workflow: the plugin's definition names the steps, and an agent reaches only those, with the role its access gives it.
  • A workflow built in the Studio can now name the steps that wait for someone: while a record waits in such a step, it shows among that person's open items, and it disappears once the step is settled.
  • You can invite people your calendar is shared with to an event. They see the invitation in their open items, answer with accept, maybe or decline, and the meeting then appears in their own calendar too. Changing the time or place asks everyone again.
  • A workflow built in the Studio can now gain new steps, states and events, or changed conditions, as an update you see listed and confirm before it applies; removing a step or a state still needs its own migration.
  • Apps that sign in with a published client description and authenticate with their own key are now recognised as such, and their sign-in errors follow the current draft standard.
  • Long exports and large writes can now run in the background for AI apps that support MCP tasks, such as Claude Code: the app gets a handle at once and fetches the result when it is ready, instead of waiting until the connection times out. Other apps keep getting their answers exactly as before.
  • A conversation in Sessions can now point at a decision, open question or action from a meeting, for example to prepare the follow-up meeting.
  • A plugin's optional client setup guide, such as the one for recording sessions, is now also available as a skill, so clients that read skills find it next to your own.
  • An app can now ask only to file and follow your own feedback reports, without access to the rest of your context.
  • Support tools that connect over MCP can now search the feedback inbox by title and pick the same tabs as the browser inbox, so a possible duplicate is found before a new report is answered.
  • Agent owners can now allow an agent to file feedback reports on their behalf, from the agent's action menu, and withdraw it there again.
  • Every object, fact, wiki and plugin entry now has a stable link that starts with your account's address, for example meinkontext.de/account/o/ada/objects/onboarding. "Copy link" in each detail page's ⋮ menu copies it; whoever opens it sees the entry only if they have access to it.
  • Your address is shown on the Account page, where you can change it once every 30 days. Links with your previous address keep working.
  • You can now delete the workspace of an agent you have revoked; the revoked agent goes with it. The workspace of an active agent still cannot be deleted; revoke the agent first.
  • When two changes to who may write arrive at the same moment, an agent's write through meinKontext now gets a "busy, nothing changed, retry" answer instead of an unexplained failure.
  • Saving and forgetting memories from a connected AI client works again; since the previous release such calls ended with an unexpected error.

15 November 2026

  • A very large upload over MCP no longer brings down the server that receives it; when the server is already busy with large uploads, a further one is asked to retry a moment later.
  • The account pages load faster on slow connections: their files are now sent brotli-compressed, and the workspace picker loads after the page has appeared instead of before it.
  • A change that runs into your storage limit now says so, instead of reporting a temporary failure that never goes away.
  • The help pages now name the Memory page, the "All workspaces" choice and the "Releases and publishing" entry of the Plugin Hub as the account shows them.
  • When renewing a connection's access failed halfway through, the connected app could lose its access and had to be authorized again. Such a failure now leaves the previous access intact, and the app's next attempt renews it normally.
  • When nothing waits for you, an agent asking for your open items now learns that in a single request instead of several.
  • Open items about your agents now appear under the agent's own workspace instead of your Standard workspace.
  • When a link opens a vault entry that does not exist or that you cannot read, the Secrets page now says the entry is unavailable instead of loading forever.
  • In the context explorer's view of all workspaces, two memories with the same name in different workspaces now both appear, each with its workspace's name after the file name, and each opens and saves on its own.
  • Under "All workspaces" the fact map now shows a fact of the same name from two workspaces as two separate nodes, and each node opens its own fact.
  • The map of a large wiki opens much faster: it now reads all of the wiki's articles in one step instead of a hundred at a time. What the map shows is unchanged, and you still see only the articles you may read.
  • Agent connections keep working after a plugin update that changes nothing an agent can reach; only an update that changes what an agent may see or do asks you to connect the agent again.
  • A single network address can no longer flood the credential check behind every request: each address gets a fixed budget of checks, and a client above it is asked to retry a few seconds later.
  • If deleting your account could not be completed within a week, your account now stays and the overview asks you to decide: delete it again or keep it.
  • Agents can now ask when you are busy without seeing your appointments: they get only the busy times of your confirmed appointments and work blocks, with no titles, places or other details.
  • An agent connected to one of its workspaces is now told when the objects there change, so it no longer has to keep asking.
  • Agents that load skills under the newer rules of the skills standard, such as Hermes Agent, now also accept the skills meinKontext publishes over an older protocol connection.
  • A connected assistant that listens for changes now learns right away when the tools of a connected integration change, so it no longer works from an outdated tool list.
  • A connected assistant that listens for changes now also learns right away when a plugin is turned on, turned off or updated for your account, so its list of tools stays current.
  • An agent of yours can now connect as a machine client without a browser, using credentials you issue for that one agent. They reach only what the agent may reach and stop working as soon as you revoke the agent or its credential.
  • Hint and secondary text is slightly darker, so it is easier to read.
  • The overview's action items now say which workspace an invitation, an agent's request, an object decision or a custody offer belongs to: your Standard workspace.
  • For connected agents and platforms: the tools that list your collections (task_collections, calendar_collections, contacts_collections, messages_channels, wiki_collections) now answer each one with a home field in place of workspaceId and workspaceName. Your own workspace appears there with its id and name; a collection someone shares with you names the sharer's workspace by its id only.
  • When you give an agent access to memory, you now choose the workspace first and then the facts in it; the separate "Personal memory" choice is gone, because every fact belongs to a workspace.
  • Under "All workspaces" the memory page now lists a fact once for each workspace that holds a fact of that name, and each entry opens its own fact.
  • The memory page under "All workspaces" now updates by itself when a fact changes in any of your workspaces, also when the change comes from another device or an agent.
  • Every context object now lives in exactly one workspace. Adding an object to a workspace moves it there from the workspace it was in.
  • When someone deletes their account, the collections they kept in a shared organization now stay in a workspace: they move to the organization owner's Standard workspace, so the other members keep their records.
  • After signing in with a provider for an integration, you always land in the workspace where the connection is stored: the one you started in, or, if you started in the view of all workspaces, the workspace that holds the connection.
  • Invitations again respect the sign-up allow-list: an invitation is only sent to an address that may sign up.
  • The account export now writes its archive piece by piece and runs one at a time per person, so a large export no longer slows the service for others.
  • The view of all your context is now called "all" everywhere: use ?workspace=all on the connection address, or "all" when you switch your start view. The old name "default" is no longer accepted and the answer says what to use instead.
  • Opening a large task list or switching workspaces no longer makes the page load the same data dozens of times in the background.
  • Switching workspaces and editing many tasks in a row no longer makes the account pages slower over time.
  • Going back from a task to the task list is faster, and an open choice in a row stays open when the list updates around it.
  • The task list and its search answer faster, most of all in a workspace that holds few of your tasks.
  • Paging through the task list is faster: the rows on screen are reused for the next page instead of being built anew.

14 November 2026

  • The privacy policy and the docs now say precisely what runs inside meinKontext: no generative AI. The one exception is a small local search model inside meinKontext, a temporary test of how well search performs with it; no data leaves meinKontext.
  • You can now keep meinKontext open in more than six browser tabs at once. Until now the seventh tab stopped loading, because the first six had taken every connection a browser allows per website; pages and live updates now share one connection.
  • Projects from Tasks now show on the memory entries, context objects and wiki articles they are linked to: in the detail as "Project", for memory entries and context objects with a link to the project, and in the list next to the entry. An agent links a project to an entry; the field disappears when Tasks is switched off and comes back when it is switched on again.
  • An agent that reads a context object now also sees the project it is linked to, as it already did for memory entries.
  • Access panels and messages show the names you gave linked contacts.
  • An agent that reads your Messages inbox now sees which channel each new notification belongs to, and dismissing a notification confirms which one was dismissed.
  • When an AI agent addresses your tasks with the wrong owner, the refusal now tells it how to find the right one.
  • A request's thread names the people asked for a reply by the names you gave linked contacts.
  • An organization API key now reads the memory of the workspace it was issued for, so recall, the status counts and the connection's fact index answer for it again.
  • Deleting an account no longer fails when the background service is reading the same data at that moment.
  • The Context Explorer shows your memory facts from all your workspaces, including facts an agent wrote into a workspace other than your standard one, and a single workspace view shows that workspace's facts.
  • After a plugin update, an agent's credential no longer works for that plugin. You now see this as an action item for the agent, and its page names the updated plugin and tells you to issue a new credential.
  • The agent is told the same: instead of an empty answer or an unexplained refusal it learns that its credential is outdated and that its owner has to issue a new one.
  • When you search a list, the words you searched for are now highlighted in the results, the same way on every page: context objects, buckets, workspaces, agents, plugins, tasks, messages, calendar, contacts, meetings, sessions, secrets, integrations and wikis.
  • Deleting an account no longer fails when the background service is reading the same data at that moment.
  • After sending an invitation, the page no longer briefly says that no invitation has been sent yet.
  • An app update that is ready now takes effect promptly after a page change in Chrome and Edge, even while other open tabs keep loading data.

13 November 2026

  • When an agent tries to send something that needs your approval, it now tells you that you approve it in meinKontext's review, not in the chat. An approve button inside a chat cannot do that, so nothing happened there before, without any explanation.
  • The start page, the documentation, the legal pages, the beta-access form and the sign-in pages are now delivered as prepared static pages. They look and read as before and load without waiting for the server to build them.
  • The beta-access form still works without JavaScript.
  • Your account pages and the plugin pages now run in the new web app. It loads once and then switches between pages without reloading.
  • If a tab that was open before the switch shows an error, reload it once.
  • Since 12 November, the pages of the plugins run on the new platform: tasks and projects, calendar, messages, contacts, secrets, integrations, wikis, the context explorer, the plugin settings, the plugin builder and the plugin hub. Your entries stayed where they were; nothing had to be moved or set up again.
  • Withdrawing access for an app you connected more than once now ends exactly that connection at once. Until now the withdrawn connection could keep working for up to an hour while another connection of the same app was still allowed.
  • After you save a contact, the confirmation stays visible while the contact refreshes. It clears when you edit the form again or close it.
  • Contact lists now load small thumbnails while profile details retain the larger image. This reduces image downloads without losing the existing photo or the ability to render other sizes.
  • If someone in one of your buckets deleted their account, that could block you from deleting yours. It no longer does: a deleted account leaves the buckets of other people.
  • An API key of an organization that was deleted with its only member's account no longer answers.
  • In an organization with several members, a member without the owner or admin role now sees only the objects shared with them, with one of their teams or with the whole organization in the object list. Objects other members keep to themselves are no longer listed.
  • The object counts on the overview, in the list's type bar and in the status an agent reads follow the same rule, so they no longer include objects a member cannot see. Owners and admins still see and count everything in their organization, and nothing changes in a personal organization.
  • A correction to the note about the object list in organizations with several members: a member without the owner or admin role sees their own objects there as well as the objects shared with them, with one of their teams or with the whole organization.
  • The size of the archive on the overview and in the status an agent reads now counts only the archived objects that member can see.
  • Live updates on the objects page now follow the object list. In an organization with several members, a member's open page was told the internal id of objects shared only with others, and when they changed; names and content were never included. A member is now told only about the objects they can list.
  • In the German interface the area for agent sessions is now called "Sessions" instead of "Gespräche": in the navigation, as the page heading and in the guide. The names of the single entries and the English interface follow later.
  • On phones and tablets, the controls of the app authorization page and of the Calendar, Sessions, Meetings and Tasks pages are now large enough to tap. A very long application name on the authorization page now wraps instead of making the page scroll sideways, and the language switch no longer covers the heading when you scroll.

12 November 2026

  • After a restart of the shared cache, the access request form no longer turns away the first person who asks; the short protective pause now starts with the restart itself.
  • Since the night of 11 to 12 November, agents reach meinKontext through the new platform services. Clients that were already connected are expected to keep working without a new authorization.
  • If a client still shows an old tool list or old instructions, reconnect it once.
  • Live updates on plugin pages no longer break off every few seconds when the database answers slowly.
  • A saved Tasks view is now visible only to the person who saved it, also in shared task lists.
  • A contributor in a shared task list can again save projects and milestones and create tasks while someone else keeps a private view there, and finds the views they saved in a shared list in the new interface.
  • Opening Tasks or Messages a second time after visiting another page, such as the overview or the memory, no longer ends on "This page could not be loaded."

11 November 2026

  • The guide to agents now shows which MCP tool performs each step of the Agents page, and which steps stay outside MCP.
  • Agents can now keep working notes in their own home workspace.
  • Object pickers in shared organizations show only objects you can access.
  • The sharing panel in the new interface can exclude a single person explicitly again, as before: tick "Explicitly exclude access" for a member, and that person loses access they would otherwise have through the organization, a team or a bucket. Excluded people are listed with a button to lift the exclusion, and a person's role stays when you exclude them or lift the exclusion.
  • The calendar list now shows the workspace of your events.
  • In the context explorer, open folders, folder pages and the file search are now part of the address: reloading the page, sharing a link or going back and forward restores them, and opening folders or searching no longer asks about unsaved changes.
  • An object that lies in several workspaces now shows all of them in the context explorer, and a file whose object was deleted in the meantime shows as no longer available while the rest of the explorer keeps working.
  • A credential opened by link shows its workspace. Longer values, such as certificates and key files, are no longer refused at 256 KiB.
  • Open suggestions to see their full details and follow accepted suggestions to their tasks. Older links to projects and milestones open again.
  • The project and milestone filters in Tasks find every project and milestone, not only the first thirty.
  • Task, project and milestone rows show which of your workspaces they belong to again; tasks shared with you by someone else show no workspace.
  • The Projekte view has a search field again; it searches all projects, and the search stays in the address when you reload or go back.
  • A bucket now links each of its shared objects to the object's content, so you can read what a bucket holds straight from its page.
  • A bucket's objects can now be read right on the bucket's page, one after the other, without leaving it.
  • Taking an object out of a bucket is now a small icon button, and it asks for confirmation before anything is removed.
  • An agent can now create buckets of its own in its workspace and fill them with objects from there; only you add members.
  • Every bucket now belongs to one of your workspaces: a bucket you create on the website lands in your Standard workspace, one your assistant creates for you lands in the workspace its connection uses, or in Standard if it uses all of them.
  • Before you delete your account, you decide about every bucket you share with others: hand it over to one of its members or delete it, one by one or all at once. Buckets nobody else belongs to are deleted with your account.
  • An agent that creates an object under a name that is already taken now learns that, and is pointed to the existing object when it may see it. Until now it saw an unexpected error.
  • When an agent's write is refused, the agent now learns why: which field is invalid or which rule a file breaks. Until now it only saw an unexpected error and retried in vain.
  • The memory page's "All workspaces" view shows the facts of all your workspaces again, and forgetting a fact there changes it where it lives.
  • Searching a large wiki answers quickly again: a search over thousands of articles now takes a fraction of a second instead of many seconds.
  • A workspace that is an agent's home can no longer be deleted. A clear message says so, instead of the agent silently losing its home.
  • If you try to delete a workspace that is an agent's home, the message now says only that it cannot be deleted. It no longer suggests moving or removing the agent first, because neither is possible yet.

10 November 2026

  • Parallel token refreshes no longer invalidate a connector's newly issued or independent grants. Identical retries within 30 seconds reuse the first rotation response; sign-out, session expiry and consent behavior are unchanged.

9 November 2026

  • The client setup guide now includes Kimi Code CLI, with personal sign-in, optional organization API keys, and notes for user and project configurations.

7 November 2026

  • When the action items could not be loaded in full, every place that lists them now says that the list may be incomplete: the overview, the agents page and the pages of Tasks, Messages, Integrations and Secrets. Each offers a way to load it again, instead of showing a partial list as if it were complete.
  • If the list of action items could not be loaded at all, the Tasks and Integrations pages now say so and offer to load it again, instead of showing no list.
  • Turning two-factor authentication on or off no longer reloads the security page, so its confirmation stays visible.
  • When your session ends elsewhere, an open page now takes you to sign-in instead of showing "not available", and turning on two-factor authentication no longer makes the security page unavailable.
  • The new app now has the Buckets and Workspaces pages with everything the current pages offer: create, invite and remove members, answer invitations, share objects or plugin content as a whole, set editing rules, pick the start workspace, add objects and move plugin content.
  • Before a member is added or removed or content is assigned to a workspace, the page now shows what becomes visible or stops being visible.
  • Wikis have their Files tab again: you can open an article's file, edit it, save a draft, review the changes and publish them, and an article you can edit links straight to its draft.
  • The context explorer now runs on the new web app: folders, search, editing, reviewing and publishing files work as before, and the records of a removed plugin show as not available instead of breaking the page.
  • A contact from another account that is linked to an event shows its name on the event again, as long as you can still see that contact.
  • Renaming a connection right after adding the first one in a workspace no longer loses the typed name.
  • When you edit a vault entry that changed in another tab and the newer version cannot be loaded, the editor now offers to load it again instead of leaving saving blocked. If the other tab removed a field you had typed into, the editor tells you and lets you keep your input as a new field, copy it or discard it before saving.
  • Every custom field of a vault entry now keeps its identity across saves, so removing one field no longer mixes up the values of the others. A copied value is cleared from the clipboard after 30 seconds only if you have not copied something else since, where the browser lets the page check.
  • On the new task page you can again move a task to another workspace and manage who can see your tasks: people with a role and buckets you share them with.
  • On the new contacts pages you can share a single profile with a person, a team, your whole organization or a bucket again, and manage who reaches all contacts of a workspace.
  • On the new wiki page you can move a wiki to another workspace and share the whole wiki through a bucket; articles added later are shared too.
  • On the new pages for secrets, integrations and the calendar you can again see and change which workspace an entry belongs to, and share a calendar's workspace with people and buckets from its settings. Message drafts show their workspace again.
  • In the new interface, plugins from the plugin builder appear in the navigation, and plugins shared with you appear there with the name of the account that shares them.
  • The public plugin hub works again without an account in the new app: anyone can browse the published plugins, open one and download its definition.
  • An object your team may read now opens and shows up in the search, not only in its version list.
  • An owner can approve or reject an AI agent's pending request again while a workspace is selected.
  • An AI agent can now link a calendar work block to a task: task search results include the reference the calendar needs.
  • The bucket list marks only static buckets; "agent-managed", the usual mode, now shows only in the bucket's own view.
  • The confirmation shown after turning two-factor authentication on or off now stays on the page; it used to disappear a moment after it appeared.
  • Plugins can now offer reports as data: an agent asks for a report over everything you may read and gets a table back, which can also be exported safely as a spreadsheet file.
  • Tasks offers reports to your agent: unowned work, handovers still waiting for an answer, what was finished or reopened in a period, how ready each milestone is, and a count by status.
  • Calendar offers reports to your agent: what is coming up in a period, how much time goes into meetings each day, and how much of each day is already taken.
  • Messages offers reports to your agent: open requests per channel and which have expired, how quickly requests were read and answered, and which drafts are still saved.
  • A question prepared from a saved draft takes over its channel and text, and once it is sent the draft is done and leaves the list.
  • Tasks, Calendar and Messages each get a reports page in the new interface: pick a report, set the period, read the table and export it as CSV or Markdown.
  • A saved draft can now be set aside directly from the drafts list, and a draft that was already sent can no longer be sent a second time.
  • A question started from a draft is sent only once, even if it is sent from two windows at the same time.
  • If the list of action items could not be loaded in full, the navigation no longer shows a number that might be too low. The page it leads to says that the list may be incomplete.
  • Links to documents stored alongside a shared context now open the right file in meinKontext. Supporting text stays in the reader; PDFs and other attachments download directly with the existing access permissions.
  • In an object shared with you, links to its other files now work: supporting documents open in meinKontext, and attached files such as PDFs download, always under your current access.
  • Answers over MCP need fewer round trips to the database, so searches, listings and connecting are quicker.
  • The view across all your workspaces stays, now as a choice of its own: links to it always say so, and nothing is listed or stored under "no workspace" any more.

6 November 2026

  • Before you share a bucket with someone, move something into a workspace or change what one of your agents may use, agents connected to your account can now ask what that person or agent would see and be allowed to do afterwards. The answer comes from the same checks as the change itself, and nothing is changed by asking.
  • On the new account surface, the custodian of a bucket can hand it over to one of its members, and the custodian of a workspace to someone in the same organization. The offer waits in the other person's open items until they accept or decline it. Only the person themselves can accept, in their browser, on a page that lists what moves and what stays behind with the rights each part carries; they also decide whether the previous custodian's agent access stays valid or is revoked. Areas that hold passwords or act in other services stay with their custodian and are handed over one at a time, each in a workspace of its own. The handover becomes available once the new account surface serves your account.
  • The new Agents page shows again what the previous one showed: open items at the top, the write permission of each shared area right in its row, the connection state with its button, and the permissions of external connections with an edit dialog. A fact an agent proposes is reviewed as a fact.
  • In the new interface, a task's page now shows everything around the task again: its properties and description, relationships to other tasks, what it is waiting for and your answer, the activity with comments, who is responsible and offers to take it over, linked contacts, conversations and planned time, and where an imported task came from.
  • The task list gains the inbox and the reports again, shows news about assignments and unfinished imports, and lets you create tasks, projects and milestones and export your tasks.
  • Hub moderators now see public plugin submissions that wait for their decision among their open items, with a link straight to the moderation page.
  • Hub moderators can now dismiss a report on a public plugin. Open reports appear among their open items until a moderator dismisses them or locks the plugin.
  • On the plugin hub's new pages, a refused rating or report keeps what you typed and shows the reason next to the form. A rating whose answer got lost no longer holds back installing or reporting, and cancelling the form lets it go. Moderators can dismiss a report from its menu.
  • An organization API key is now read-only for memory as well: it can recall facts, but saving or forgetting them needs a signed-in connection.
  • A read-only connection can no longer read unpublished drafts through a resource address; it now sees only what the object tool shows it.
  • An agent access or read-only access that an app created with your sign-in now ends as soon as you withdraw that app's access, the app is disabled or you sign out of the session it used.
  • The contact actions next to a person's name (create a contact, link an existing one, open the contact) now appear wherever a person is shown, in tasks, calendar sharing, messages and sharing lists, not only in buckets.
  • Links in wiki articles, memories and context objects are now rendered more strictly, so crafted content can no longer smuggle executable markup into a page.
  • The account export now contains only the context objects you can read yourself, not those of other members of your organization.
  • Selecting a bucket, workspace or agent now only swaps the detail beside the list; the page and its navigation no longer reload.
  • IDs, addresses and other technical values look the same everywhere and carry a small copy icon; a workspace's address shows as a full-width field with the icon inside it.
  • The detail panel beside a list scrolls with a thin, unobtrusive scrollbar.
  • A refused change, such as deleting something that is already gone, now shows its reason and keeps what you typed, instead of making the whole area unavailable.

5 November 2026

  • The new interface can be installed as an app. Updates preserve unsaved edits, and an offline start shows no personal data.
  • Bucket owners can let members edit shared objects directly or submit changes for approval. Another owner's object requires their consent first. Proposals appear in action items and retain their version history.
  • Reset an object's editing setting to follow its bucket's rule, including later changes.

4 November 2026

  • The Agents page now starts with a list of all your agents, showing at a glance whether each one is connected and whether something is waiting for you. Opening an agent shows its access and its connection in two clear sections; further actions such as checking access or revoking the agent sit in its "⋮" menu, and revoking asks for confirmation first.
  • The integration directory lists Google Meet. Once Google Meet is set up for this service, you can connect your Google account and read your meeting records, participants and transcripts; until then the entry says that setup is still missing.
  • Agent connection reminders perform less repeated work for large access lists. The rules for deciding whether a new connection is needed remain unchanged.
  • Opening several shared folders avoids reading the same directory information repeatedly. File access still checks current permissions.
  • The context explorer opens folders and files faster, especially wiki folders with several open branches and content shared by other people.
  • The context explorer avoids an unnecessary wait for ongoing storage cleanup when listing folders and filenames. Access checks and the displayed contents remain unchanged. Further performance work is still in progress.
  • Agents with their own access key get answers to searches and article reads faster, especially for articles with many files.
  • The Workspaces page avoids preparing every hidden move list at once. Opening and reopening a move dialog retains its pending actions and feedback. Bucket forms likewise prepare on first opening and retain drafts when reopened.
  • Memory, context objects, buckets, workspaces and agents now share one way of listing: a search bar, the number of entries and plain rows. Opening a bucket, workspace or agent shows its details beside the list, as memory and objects already did; on a phone the details replace the list and "Back to list" returns.
  • What waits for you now looks the same on every page and sits at the top, the Agents page included: a proposed change to review or a connection to renew shows there, as invitations do on Buckets and open items in Tasks, Messages, Secrets and Integrations.
  • MCP apps can discover the permissions needed for a regular connection without requesting support-only access. This fixes a sign-in failure seen with Grok Bot.
  • Pure human catalog and inspection calls use PostgreSQL READ ONLY and no longer wait for the storage accounting lock. Writes, audited reads and record batches retain their existing checks.
  • "Apps & API keys" moved from the main navigation into the account menu at the bottom of the navigation, next to your account settings and invitations.
  • Leftover data of a plugin that no longer exists is removed, so the context explorer no longer shows entries that fail with an error when opened.
  • The note that your knowledge stays under your control now appears on the overview only next to the button for connecting an AI app, and disappears with it once an app is connected.
  • On the workspaces page, copying a workspace's address is now an entry in the card's menu instead of a separate button next to the address.

3 November 2026

  • Changes your agents propose now appear under Action items and lead straight to the review. So does an agent whose new access only takes effect once you connect it, and an external action of your own that waits for your approval.
  • Rejecting an agent's proposed change now closes the review and says it was rejected, instead of leaving the dialog open with the approval message.
  • Searching large wikis answers much faster.
  • On the buckets page, each bucket's actions (invite a member, share objects or a whole wiki, allow or revoke agent access, delete) now sit in a menu at the top right of its card and open in a window over the page; the search for known people is part of the invite window.
  • A new bucket is created with the button at the top right, which asks for the name and whether AI apps may manage the content.
  • The "Buckets" entry in the navigation shows how many invitations are waiting for your answer, like the plugins show their open items.
  • At the top of the buckets page you now only see invitations waiting for your answer; the invitations you sent, with the option to withdraw them and their history, open from the menu of their bucket.
  • When the Contacts plugin is active, people in your buckets and invitations can be turned into a contact or linked to an existing one from the menu next to their name; from then on you see your contact there instead of the bare account, and only you see this link.
  • Tasks, Messages, Calendar and sharing lists also show your contact's name for people you have linked.
  • The Buckets page avoids counting the same Wiki twice and loads independent owners' summaries concurrently. Article totals, sharing options and access checks remain available.
  • Large context counts avoid looking up dependencies that are already loaded. Access and version checks remain unchanged.
  • Opening a nested Wiki folder directly in Context Explorer avoids reading the same directory metadata twice. Collapsed folders, pagination and access checks behave as before.
  • Browsing Wiki and plugin folders in Context Explorer avoids unnecessary reads of unrelated files. Access checks and folder navigation remain unchanged.
  • Context Explorer loads independent owners' folder metadata concurrently, so shared Wiki folders open sooner. Folder contents and access checks remain unchanged.
  • Plugin management reads plugin information and available integrations together. Permissions and available features are preserved.
  • Pure account inspection can proceed alongside an account write using a consistent snapshot. Audited reads and commands retain their existing coordination and permission checks.
  • Large context counts avoid repeated database parent checks while continuing to evaluate current access rights and selected versions. Overview and Workspace loading benefit from this change; production timing is verified after release.
  • Workspace pages prepare their plugin lists concurrently to reduce waiting.
  • Workspace pages can start counting one owner's entries while another owner's lists are still loading.
  • The overview is quieter: the line with connected apps and last activity, the "Memory" link next to your knowledge and the footnote about app access are gone.
  • The button next to an object in a workspace now says "Remove from workspace" instead of "Hide from this view"; the object itself stays in your context.

2 November 2026

  • The overview and Wiki list load information from your own and shared Wikis with less waiting. Access checks and displayed counts remain unchanged.
  • Server-side Workspace diagnostics distinguish metadata, plugin inventory and count calls by known plugin. Bounded phase labels contain no workspace, organization or record identities; unknown plugins are grouped together. Queries, results and permission checks are unchanged.
  • On the workspaces page, each workspace's actions (set as start, add objects, move plugin content, delete) now sit in a menu at the top right of its card, and adding objects opens the selection in a window over the page.
  • A new workspace is created with the button at the top right, which asks for the name in a small window.
  • The week view marks the current time with a red line, appointments are no longer see-through, and the calendar list beside the grid starts folded.
  • Plugin pages in a selected workspace load their pending-action notices without scanning large collections in other workspaces. Access checks and notice contents remain unchanged.
  • While a page, tab or list loads, its loading placeholder now has the shape that view had the last time you saw it, so nothing jumps when the content arrives. The placeholder keeps none of your text.
  • Large Workspace and Overview counts do less database work while retaining the same access checks and results.
  • Opening large Wiki folders in the Context Explorer performs less database work while preserving the same files, folders and access checks.
  • A production release started from an internal documentation update now automatically selects its verified application build. The release report shows both commits, while all existing release checks remain in place.
  • Support staff: changes to a report's status, category, priority and assignee are saved right away, without a separate Save button.
  • The Explorer avoids repeating the same Wiki metadata scan when its root and a subfolder are open together. Files, folders and access checks remain unchanged.
  • Account navigation avoids loading expensive pages twice when a hover is followed by a click. Pages still check your current access when you open them.
  • Nested Wiki folders can show their immediate files and subfolders without building the entire Wiki catalog. File access, search and export behavior remain intact.
  • Opening the Wiki list avoids repeated lookups when your account includes your own and shared wikis. Access checks and all list contents remain unchanged.
  • Fixed an executor packaging failure that blocked deployments after an authentication logging security update. The security update remains in place.

1 November 2026

  • Workspace and collection counts avoid a repeated database scan for large context collections. Counts and access restrictions remain unchanged.
  • Workspace counts load related task records with fewer database requests while preserving current access checks and exact counts.
  • Large Wiki folder overviews can discover their directories without loading every document. Opening files, searching and exporting retain their access checks and full validation.
  • Context changes avoid unnecessary database compilation work, reducing the time that concurrent page loads may wait for a write to finish.
  • Large Wiki folders avoid a costly database preparation step that could delay opening them by several seconds. Shared folders also avoid repeatedly loading unreachable files. Workspace and collection counts also avoid premature full edition scans and repeated permission-data reads. Access checks and available files are unchanged.
  • Agents get a much shorter plugin description by default and fetch a single schema only when they need it.
  • The context explorer avoids repeated searches through unrelated shared files when opening folders. Workspace counts also avoid an expensive fallback when an existing share supplements direct access. File visibility and editing permissions remain unchanged.
  • Workspace inventory. Workspace content counts use fewer repeated access checks while preserving individual restrictions, revoked access and version selections. Production speed is being verified after release.
  • Explorer folder browsing. Expanded plugin folders share their filename lookup within one page load. Opening a file checks that file directly. Existing access restrictions, file versions and folder pagination remain in place.
  • Overview and Objects. Overview avoids repeated count evaluations for the same plugin. Objects loads independent metadata together while keeping workspace restrictions, filters, pagination and error reporting.
  • Large Wiki folders. Source metadata uses fewer repeated authorization reads. File versions, complete metadata and live access checks remain unchanged.
  • The favorites view of your password vault opens again.
  • Workspace inventory counting. Counts now group equivalent current-version records as well as published-channel records. Source-file access dependencies and individually restricted records retain their full permission checks.

31 October 2026

  • Keep agent conversations across clients, import selected transcripts, save cited handoffs and share a conversation through a bucket. Later entries follow the same share; other conversations remain private. Search originals and results in a focused library, reopen cited source revisions, and archive or restore conversations. Permanently delete an archived conversation with explicit confirmation.
  • The search in the Add access dialog of an agent now finds everything in your account while you type, and the separate account search button is gone.
  • Large object lists and Wiki counts require less repeated work when opening account pages. Lists keep their exact counts, access checks and selected versions. Bulk operations read document contents in batches.
  • Overviews that show how many records you have, such as workspaces, objects and wikis, load faster when you have a lot of records.
  • Lists and summaries avoid redundant database work when selecting document versions. Sharing, personal version choices and permission checks are unchanged.
  • Opening a Wiki article avoids loading every article into the permission-checking stage. This reduces work for large Wikis while preserving shared access and selected versions.
  • An app you connected with a device code now appears as its own entry among your connected apps. Removing that entry ends the app's connections made with a code, on every device, and leaves its other connections in place.
  • The calendar page opens again when Calendar is turned off for your organization. It showed an error instead of your calendars.
  • In the overview of all workspaces, a calendar's sharing note now says for every workspace that calendars created there later are shared too.
  • The Buckets view loads Wiki counts and metadata together for the linked Wikis, reducing repeated queries. Access checks and the displayed contents remain unchanged.
  • Wiki writes avoid repeating the same article lookup during restoration and update preparation. Access checks and subsequent writes remain up to date.
  • The Context explorer performs fewer repeated permission queries when files from several plugins are available. File visibility and access checks remain intact.
  • Storage quota checks avoid expensive query compilation, shortening accounting while organization writes hold their lock.
  • Wiki lists avoid repeated discovery and unused workspace lookups. Counts remain limited to the wikis visible in the current view.
  • Workspace record counts avoid repeated permission processing for published content while retaining live sharing and access checks.
  • Agents can now be given access to workspaces, buckets, objects and facts on accounts with many memories. These requests used to fail with an unhelpful message, which now says what to check.
  • The Objects view calculates its type counts together instead of querying each type separately. Access checks, selected versions and archived-content handling remain unchanged.
  • A device you connected with a code now appears as its own entry among your connected apps, and removing it ends only that device.
  • The Context Explorer opens its top-level folders without first loading every plugin file entry. Access checks and the contents of the folders remain unchanged.
  • Workspace loading avoids counting content that is not assigned to a workspace. Repeated inventory reads also avoid reloading identical permission data, while continuing to check access for every read.
  • If maintenance starts while a page is open, the page now shows a readable maintenance notice and takes you to the maintenance page instead of a technical error message.
  • The connection guide now explains how to connect GitHub Copilot in VS Code, the terminal and GitHub-hosted tasks, with authentication examples and checks for the first tool call.
  • The overview avoids calculating wiki statistics it does not display, reducing unnecessary loading work while preserving the visible counts.
  • Review historical task amendments. Compare a changed source with existing tasks before applying selected amendments. Original history stays intact, conflicting edits remain visible, and current requests require an explicitly selected card and person.
  • The Explorer avoids processing wiki files twice. Counters load no unused record details, and action-item checks skip records without action items. Further improvements to large workspace inventories remain in progress.
  • The agents page loads its sharing choices when you open Add access. Searches process matching context metadata in smaller batches while preserving existing access restrictions.
  • meinKontext now speaks the newer MCP protocol revision 2026-07-28 next to 2025-11-25, so current MCP clients such as Claude Code connect with the revision they prefer. Your tools, skills and answers stay the same; clients that read the tool descriptions in detail see them in the current JSON Schema format, and some error messages for malformed requests are worded differently.
  • Permission checks for many individually shared records are faster. Parent and sibling content remain protected by the same access rules.
  • Agents connected with their own key get their answers faster: each request no longer reads every entry in the collections the agent may use.
  • Agent sharing choices reuse their authorization evaluation within the page load. Workspace record counts avoid loading unused records and workspace assignments. The file explorer also avoids reading Wiki article file lists a second time. These changes reduce work when accounts contain many records.
  • Plugins now update on their own with every release. Nobody has to click "Update" any more, and shared content no longer disappears because someone else has not updated yet.

30 October 2026

  • Browser tabs now name each page in your language, and plugin pages show the plugin's name instead of a generic "Plugins".
  • Clear current task notes. Agents can explicitly clear a task's current note or evidence while preserving its history. Required completion evidence stays protected, and clearing an already-empty field leaves the task unchanged.
  • Calendars are now ordinary entries of the calendar: each one carries its own name, colour, settings and archive state, and moving a calendar to another workspace takes its appointments along. After the update, an administrator confirms the new calendar version under plugins once; your existing calendars, appointments and personal settings are carried over unchanged.
  • "Connect an app" and "Documentation" are now regular items with icons in the account navigation, and the link to the product website is gone.
  • The overview offers to connect an AI app only until you have connected one yourself; a colleague's app no longer hides it, and a used API key counts as connected.
  • Agents connected to one of your workspaces again see the content you granted them in that workspace.
  • Pages with shared content load faster: the buckets page and a contact's profile need far fewer database round trips, and no page reads everything of an organization that shares something with you any more.
  • Faster agent sharing choices. The agent page avoids repeatedly searching all records for their parent. This reduces work that can also delay other account pages when the context contains many records.
  • Saving multiple records in one operation avoids repeatedly recalculating the organization's entire storage usage. Storage limits still apply to the complete operation.
  • The overview counts wikis once again: they appear as one row and one legend line, and the total in the circle no longer contains the wiki articles twice.
  • The notice that part of a plugin's content is unavailable no longer appears when the organization with the outstanding update shares nothing of that plugin with you.
  • Storage accounting gains database indexes intended to shorten checks while writes hold an organization lock. Installation uses the maintenance screen.
  • Agents working with their own access key get answers faster: each request now considers only the content the agent may use instead of everything in the account. What an agent may see is unchanged.
  • Pending-work indicators reuse database reads and focus on the selected plugin and workspace. If a read reaches its limit, the page remains usable and reports incomplete counts without immediately starting more work.
  • Pages that list sharing, participants, workspaces and records do less work per request: they now check access only for the items they show instead of for everything in the account, and the workspaces overview gathers what it shows in a few steps instead of one per plugin and account. Who may see what is unchanged.
  • The context objects page now also shows the records of your plugins, such as tasks, events and contacts. Their types can be chosen at the top of the page and in the type filter, and a record opens in its plugin.
  • Archived content no longer counts: records in an archived calendar or wiki and archived objects in a workspace are left out of lists and figures by default.
  • On the context objects and memory pages the workspace selection now sits beside the page title, in the same place as in the plugins.
  • The context objects page now also shows the records of your plugins, such as tasks, events and contacts. Their types can be chosen at the top of the page and in the type filter, and a record opens in its plugin.
  • Open items now appear beside plugins and their relevant views. Message notifications lead to the right conversation, including replies to your own questions and shared conversations. You can dismiss a notification without changing the conversation. Archived entries no longer contribute to the count.
  • Pages that list sharing, participants, workspaces and records do less work per request: they now check access only for the items they show instead of for everything in the account. Who may see what is unchanged.
  • Forgetting a fact is now one click away: the ⋮ menu at the top of an open fact offers "Forget", and for an archived fact "Delete permanently".
  • An outstanding plugin update in an organization sharing content no longer prevents compatible content from loading in Wikis and the Context Explorer. A notice explains which plugin needs an update by its owning organization.
  • meinKontext now tells connected assistants to save lasting facts only in meinKontext and never in their own local memory, and the setup rule it installs in your assistant says the same.
  • An assistant searching your memory now finds facts by each of the words it searches for, including the project a fact belongs to, instead of only by the exact phrase.
  • Loading workspace content with many tasks and projects avoids repeated database work when resolving their relationships.
  • Temporary loading failures during page changes can now recover automatically with protection against repeated reloads. Unexpected plugin failures are reported more reliably to help identify their cause.
  • Connecting an agent and listing its tools is faster again: the server now needs about half the database work for both.
  • Plugin views and agent requests that read records no longer stall for seconds on large accounts.
  • Requests from connected AI assistants answer a little faster, because the note about open items they carry needs fewer database queries.
  • Pages no longer stall when several pages, people or agents use the same account at once: reading integrations, contacts, files, sharing, workspaces and agent settings now runs side by side instead of one after another, and reading no longer recounts the storage used. Pages that could take close to a minute load much faster. The storage limit applies exactly as before to everything that saves data.
  • Connected agents get their answers faster: the server now does a fraction of the database work for every request, and a simple keep-alive check from an agent no longer loads its plugins at all.
  • Account pages and plugin views ask the database fewer questions per page load.
  • Cursor can now connect to meinKontext through automatic client registration, without setting up a client ID by hand.
  • Contact pages open faster: a contact's notes, merges, relationships and linked people are now loaded together instead of one by one.
  • Opening pages no longer stalls when several pages, people or agents use the same account at once: reading integrations, contacts, files, sharing, workspaces and agent settings now runs side by side instead of one after another, so pages that could take close to a minute load much faster.

29 October 2026

  • Search answers faster in large accounts, and short articles that are about the search term now appear above long ones that only mention it.
  • When an assistant looks up a project in your memory, the project entry now points it to the facts stored for that project instead of describing itself as an empty placeholder.
  • Listing your objects is faster for accounts with many wiki articles.
  • Opening a skill, a document version or a wiki article reads its files faster: all files of a version now arrive together instead of one by one.
  • The sidebar is tidier: memory, context objects, buckets, workspaces, agents and apps now sit together under "Context", and "Manage plugins" is the last entry under "Plugins".
  • Your open actions now belong to a workspace: an AI app connected to one workspace sees only that workspace's items, items from collections other people share with you appear in every workspace, and the account overview shows all of them with the workspace name next to each row.
  • The MCP tool that lists your open actions is now called list_action_items; the old name keeps working for apps that already use it.
  • Updating the Secrets plugin works again for everyone who installed it before the password vault existed.
  • Contacts connect a person’s separate private and business profiles. Photos, personal notes and targeted sharing stay with each profile. Compatible plugins link tasks, events, conversations and wiki articles while preserving their independent access permissions.

28 October 2026

  • Buckets now have one name everywhere: the page, the docs and the Messages channel form say "Buckets" instead of "Shared buckets". Other terms across the account, plugins, emails and docs are now consistent too, for example "AI app" for connected apps, "org API key" for organization keys and "event" in the calendar.
  • On request, the setup recipe can add short local reminders at session start and after context compaction. Existing settings are preserved; the client must trust the hooks. Removal also works offline. Other clients and agent profiles can read rules for their available tools and a local adapter contract through client_policy. Persona files remain excluded.
  • The changelog and the roadmap are now each a single list per day or per status, without the separate "For users" and "Technical" parts.
  • The MCP server can start even when the old S3 store is unreachable. Authentication and PostgreSQL are still checked before it starts.
  • Recovery documentation now describes the selected database point. Subsequent changes are not automatically included; the withdrawn additional checkpoint tooling has been removed.
  • The overview now counts everything your plugins hold: next to context objects and wikis it lists tasks and projects, events, conversations and messages, credentials and vault items, and connections, each with its own colour in the ring and a link to the plugin.
  • Overview: "Open actions" now also shows what waits for you inside your plugins: tasks offered to you or waiting for your decision, check or action, tasks due today or overdue, requests in Messages that need your reply or your close-out, channels you still have to consent to, agent actions awaiting your review, and connections that need re-authorization. Once something is settled it disappears by itself. Connected AI apps see the same actions through list_attention.
  • New content is stored exclusively in PostgreSQL; parallel writes to S3 stop. Deletion of old S3 data follows separately.
  • Overview: "Open actions" is a slim list of rows instead of a large card, with a count, the "All invitations" link and one row per action. The notes "This is a preview" and "Some open actions could not be checked" are gone: the overview now reads every organization and every notice, and a plugin without attention rules is no longer an error.
  • The meinKontext logo in the sidebar is larger.

For users

  • On your request, your agent can fetch a recipe for preferring meinKontext, check its local instruction block and remove it again. Requires personal OAuth; no automatic content copies or hooks.
  • Secrets: you edit an API access's label right at its title, and its actions (replace, disable, export, workspaces, revoke) sit in one ⋮ menu instead of expandable links. The vault's import and export are in the ⋮ menu next to "New login". Action menus open upwards when there is no room below.
  • Support team: the "Support" menu entry shows, in red, how many reports nobody has handled yet.
  • Wikis now run entirely on the Wiki plugin; the old Wiki storage is removed. Existing links, tools, shares and producer pipelines keep working unchanged. An AI agent with managed access can no longer edit articles of a producer-managed wiki.
  • Secrets is now a password vault: create logins with one-time codes, notes and cards, show and copy values, generate passwords and see their strength, look up previous passwords, a trash, import from 1Password, Bitwarden and your browser, encrypted export. Your integrations' API access sits in the same list.
  • Calendar management: a list of all your calendars sits left of the grid. The coloured dot shows or hides a calendar, the star marks the default calendar for new events, the ⋯ menu leads to settings, "only this one" and the archive. Clicking a name opens name, colour, description, time zone, default duration, filing and sharing; archiving replaces deleting. Every event carries its calendar's colour, work blocks are dashed, drafts outlined, cancelled events struck through. A calendar's sharing is now managed there, no longer on an event page. The list can be folded away.
  • Canceled tasks stay out of the task views until you bring them back through the status filter ("Canceled" or "All, including canceled").
  • Projects and milestones edit on the row like tasks do: title, status and dates, in the project list and on the roadmap.
  • Support team: the report list starts with open reports only. Resolved and closed ones are under "Done", with search and filters like in Tasks.
  • Workspace cards now also show a workspace's plugin content, such as tasks, with the number of entries. Before, they said "No context objects assigned" even when the workspace held content.
  • Plugin content no longer needs a collection: tasks, events, credentials and connections land in the workspace selected at the top. The "Create task list" and "Create collection" dialogs are gone; calendars are still created by hand and keep their colour and settings.
  • A plugin record lives in exactly one workspace. Moving a project takes its tasks along; a wiki moves as a whole.

Technical

  • S3 → PostgreSQL: All existing application content, including text and binary files, has been transferred to PostgreSQL and checked for completeness. Since 28 October, production reads content exclusively from PostgreSQL, without falling back to S3. New content is temporarily still written to S3 as well; full S3 retirement follows separately.

  • Vault entries are stored encrypted; the server can decrypt them to show them, and every reveal is logged. Agents can neither read nor fill vault entries. End-to-end encryption follows later.

  • Calendars have a profile (colour, description, time zone, default duration) and personal settings per workspace (hidden calendars, default calendar, own colours for shared calendars). Both are plugin records in the database. The Calendar plugin needs one plugin update under Plugins after this release; until then it is read-only. Renaming and archiving a collection are new platform operations open to other plugins too.

  • The old implementation's Wiki tables and their migration pipeline are removed from the database and the code; Wikis are collections and records of the Wiki plugin alone since.

  • Agents and MCP clients write without collection_id into their connection's workspace; the tool task_create_collection no longer exists.

27 October 2026

For users

  • Changelog and roadmap as documentation pages, linked from the alpha explanation in the account.
  • Open actions sit as a strip of rows under the section heading.
  • The home workspace covers the plugin content lying in it.
  • An alpha band sits above the account with an explanation of what the alpha means; landing, access page and documentation now say alpha instead of closed beta.
  • The overview turns the example prompt for your AI into a composer line with provenance and paging.
  • Task titles can be edited in place, the pencil sits right after the text.
  • Plugin content is named by its plugin, buckets sit under knowledge, the profile has a menu.
  • The maintenance page wears the product look.
  • The workspace selector sits beside the page titles, workspaces come before agents in the navigation, and the "Start · Documentation" row left the account footer.
  • Workspaces: shared assignment and a real Standard workspace.

Technical

  • The product stage (alpha, beta, regular operation) is set per environment and drives the band, its explanation, the landing, the access page and the documentation.
  • Invitations follow the same sign-up policy as registration; individual email addresses can be allowed.
  • Your content is now read from the database; the previous object store only serves as a counted fallback until it is switched off.

26 October 2026

For users

  • Object rows show workspace pills, the reader toggles workspaces; plugin views work with real workspaces.
  • Shorter memory label in the navigation.
  • Objects page with a type bar, one-click type filter and workspace scope.
  • The calendar's week heading renders the same on server and client.

Technical

  • Decision: all content, files and wiki originals included, moves entirely into the database; the object store is being switched off. Texts and binaries are written there since.
  • Decision: meinKontext is rebuilt without server-side rendering and with several instances per tier; today's interface only receives bug fixes.
  • Production runs in the same zone as the database.

25 October 2026

Technical

  • The target schema for the context store in the database is in place; files are encoded losslessly.
  • The server no longer starts when authentication cannot be initialised.

24 October 2026

For users

  • GitHub integration: private repositories and per-agent permissions.
  • Sign-up is invitation-only.

Technical

  • Wikis are migrated live; the invitation requirement is enforced at the HTTP boundary.