Get your free AI plan
Docs / Changelog

Changelog

What each release changed in a tool, a field or the name of a page, newest first, with the old name beside the new.

One entry for each release that changes a tool, a field or a page name, newest first. A change to a tool that is merged or removed has its own order and dates on the Migration page.

2026-11-21: Terms and Joins follow the design

Map › Terms is six views, with the terms and the joins each as one table. Nothing your agent calls changed.

What changed.

  • Page name. Map › Terms has a strip of six views, each with its count: Terms, Joins, Proposals from scans, Columns to confirm, Your names for objects and Rejected. “Joins as a table” is the Joins view, and an older link to a section of the page opens the view that holds it.
  • Page name. On Terms, the questions about your terms are one line, “N questions about your terms wait in Work”, with the way to decide them in place. The terms are one table: what a term means here, what each system calls it and who confirmed it. “How the glossary works” is “How terms work”.
  • Page name. On Joins, the table’s columns are Join, Key, Strength, Basis, Rows that match and State, with pills for not sure, contradicted, weak, guessed, stated by your team, proposed for removal, held and rejected. Twelve rows show at a time and Group by is gone. A banner says when join reviews wait, and “To confirm” has a Confirm N joins button.

No tool was added, renamed or removed, and no input or answer of any tool changed.

2026-11-21: Each connected system has a page

A system’s state, its data, its scans and who uses it are on its own page, opened from its name in Sources › Integrations.

What changed.

  • Page name. Every system in Sources › Integrations opens its own page: Test connection, Scan now and Remove at the top, then the connection (who connected it, when it was last read, the next scan and what it reads), the objects its files built with their record counts, its latest scans and what each changed, who owns it and which department uses it, the workflows that use it and what agents may do in it. A system that needs attention shows how to fix it. Where a part could not be read, the page says so in its place.

No tool or field changed, and no function was removed: each action the Integrations table’s row menu held is still there, and the table keeps its columns.

2026-11-21: Playbooks, Watch for and Must hold read as lists you can filter

Playbooks, Watch for and Must hold are each one table with search, filters with counts and paging, and the buttons that start a playbook or a rule sit beside the title. Nothing your agent reads changed.

What changed.

  • Page name. Workflows › Playbooks: the sections “Waiting for your decision”, “In use” and “Not in use” are one table with a status row (In use, Not in use, Proposed, Not anchored, On a schedule, May do without asking) and a workflow row. The “Needs your decision” banner is one line saying the drafts wait in Work, with the way to the task, and “How playbooks work” is said where a playbook is written.
  • Page name. Rules › Watch for: the “In use” filter is called All and there is no Working filter; a rule still says Working, and ?state=working still opens them. Three filters are new: Starts several workflows, Starts nothing yet and An agent proposes a change. “Add a rule” moved into the header, and each tab carries its count.
  • Page name. Rules › Must hold: the written policies and the rules read from your documents are one table (What must hold, Layer, Applies to, Used in, Source, This week). The Source filter is the pills Written here and From your documents, and ?source= still works. The “Decisions” section is a compact card per waiting kind with a link to its task in Work.

No tool, field or answer an agent reads changed, and every old address opens the page it meant.

2026-11-20: Each agent has a page, and Permissions and Usage are gone

What an agent may do, what it sees and what it did are on its own page. The two tabs Permissions and Usage were folded into Agents, so there is one place for agents.

What changed.

  • Page name. Every agent in Sources › Agents opens its own page: what it may do (the action, the system, how it goes and its limits), what it sees, what it did, who connected it, the workflows it works in and its count of tasks today. Copy setup prompt and Reconnect are at the top; uploads, scope, hand over only, delegate, Ask first and Revoke are under More.
  • Page name. The tab Permissions is gone. The actions your agents may take, How agents work and the licences are on Sources › Agents; what each agent may do with them is on the agent’s page. A link to the old tab, or to Policies or Actions, opens Sources › Agents.
  • Page name. The tab Usage is gone. The agent Maplith runs on GitHub has its own page, Sources › Agents › GitHub agent, with its runs, its tasks over 30 days and the daily spending limit. A builder sees the two counts on Sources › Agents.
  • Page name. Who is told about approvals, and approvals in Slack, moved to Settings › Workspace › Notifications.
  • Field. The policy_url of a denied request_action and of a refused redeem_action_grant opens the page of the key that asked, at What it may do, when the key is known. The wording of next_step names that page.

No tool was added, renamed or removed, and no function was removed: each old Permissions address answers one redirect to Agents and each old Usage address one to Sources › Agents › GitHub agent, with its query kept.

2026-11-20: The Map pages follow the design

The Map’s pages read as the design draws them: its header, the Atlas’s List, the object page and Processes. Nothing your agent calls changed.

What changed.

  • Page name. The Map’s subtitle reads “How your company fits together: its systems, its data and how work flows.” The header under its tabs is gone: the counts are one line in the Atlas and in its List, and Map confidence is a button there that opens the same card.
  • Page name. On Processes, “Deviations” is “Where it differs”, “Playbooks anchored here” is “Playbooks” and “Rules that apply here” is “Rules that apply”, and each process names the workflow that handles it, or says it needs setup.
  • Page name. On an object’s page the crumb is “Map / Atlas”, and everything built on the object (workflows, playbooks, rules, policies, metrics, automations, findings and processes) is one block, “Used by”.

No tool was added, renamed or removed, and no input or answer of any tool changed.

2026-11-20: A playbook has a page of its own

A playbook now opens on its own page from its title in the list: its text, its history, where it is used, what it applies to, what it may do without asking and the rules that apply. A playbook that more than one workflow uses warns before a change and offers a copy for one workflow.

What changed.

  • Page name. Playbook is a new page, opened from a playbook’s title in Workflows › Playbooks. It shows how to do the work in the person’s words, one row for each kept version with what changed, when and by whom, the workflows that use it, what it applies to, the actions it may take without asking a person and the rules that apply. The list still opens a playbook in place and keeps its actions.
  • Page name. A playbook that is used by more than one workflow is marked Shared and says where a change takes effect. Make a copy for one workflow makes a new playbook with the same text, anchors, trigger rules and limits, and the links to what it works on and in, in use for that workflow in place of the shared one, in one step. The copy starts with no schedule, and it starts on the same kinds of signal as the shared playbook.

No tool or field changed in this release, and no function was removed. A playbook’s text, its anchors and what an agent is served are exactly as they were.

2026-11-20: Workflows: a table of workflows, a page for each, and one New workflow

All workflows is now a table with search, a status filter and a sort that puts what is waiting on a person first. A workflow and a department each have their own header, and Runs outside Maplith moved under All workflows.

What changed.

  • Page name. Workflows › All workflows is a table of every workflow with its department, status, tasks this month and the tasks waiting on a person. The section Runs outside Maplith is at its foot, where departments and the systems layer are on; elsewhere it stays at the foot of Workflows › Playbooks.
  • Page name. A workflow now has its own tabs: Overview, Work and, for the account’s owners and admins who see the whole map, History. A department’s page shows its work right now, its findings as New or Covered, and the playbooks and rules not yet in a workflow. New workflow is one button in the header of Workflows › The chain and Workflows › All workflows.

No tool or field changed in this release, and no function was removed: every action the old lists and pages had is still there. Old addresses of All workflows keep working and ignore the grouping and department filter they carried.

2026-11-20: A finding has its own page, and Handle it every time is a page

Each finding in Findings now opens on a page of its own, where you decide what should happen with it. Setting up a workflow from a finding is a page too, with the five parts filled in from the finding. Recently decided lists what you decided, where it went and who decided it.

What changed.

  • Page name. Findings lists every finding as one row with one button, Decide, and opens the finding at /findings/<id>. The finding's page holds what Maplith found, the evidence, where it comes from and the three answers Fix it once, Handle it every time and Not a problem. The row that opened and closed in place is gone, and so is the old address /findings?finding=<id>, which now answers with a permanent redirect to the finding's page.
  • Page name. Handle it every time is a page under the finding, at /findings/<id>/workflow, where a workflow is named and created with its five parts filled in from the finding. It replaces Make a workflow and Add to a workflow inside the row; adding the finding to a workflow that exists is on the same page. A hand-over that waits for a person reads Waiting on a person.

No tool was added, renamed or removed, and list_findings and get_task_context answer as before. Linking a finding to a workflow still changes no status.

2026-11-20: Work opens on the board

Work opens on its board, with four chips, a filter bar and a card for each task. The list is a table for each status, a task opens beside it, and Results counts tasks.

What changed.

  • Page name. Work › Board is where Work opens, as the first tab. It groups the tasks by status or by who has them, and a card is one link to its task. Work › List is a table for each status with who has it, its workflow, how long it took and its tokens, and the page has an Export that saves the tasks the filters leave as a CSV file.
  • Page name. A task opens beside the list instead of replacing it. A signal’s moves (take, plan, let go, mark done, reopen) are in the task, not in the list. Work › Results shows six figures, a table by workflow and how the done tasks ended, and says tasks where it said signals.

No tool or field changed. list_signals and get_task_context answer as before, and every old address still opens the list or the task it meant, with its filter.

2026-11-20: One summary for a rule, in place of a signal per record

A rule can now raise one summary per check that says how many records match and names the first of them, and every rule Maplith sets up itself does.

What changed.

  • Field. A rule_fired signal of a rule set to one summary per check carries payload.rollup with count, groups and first (the first ten records by key, each with its figures) and no group. Its dedupe key ends in :rollup, a count at or below the count it was decided at is not a change of the signal while a rise above it reopens a dismissed or handled one (the count at the decision is kept as rollup.decided_count while it stays done), and get_task_context forecasts no action on it, as on the flood-cap summary. list_signals counts its count into the rule’s groups.
  • Field. Once nothing new holds, a summary is answered the way a group’s signal is: it resolves itself, and the clear is recorded on the rule’s own record.

No tool was added, renamed or removed, and a rule that raises a signal per record raises exactly what it raised before.

2026-11-19: Workflow answers made exact

The workflow fields your agent reads now follow what is in use: a draft playbook sits in its workflow without starting anything, a rule’s signals go to that rule’s workflows only, and a filter on a workflow that does not exist answers at once.

What changed.

  • Field. A draft playbook placed in a workflow is listed there but takes part in nothing: it does not start the workflow, link a rule or receive signals, and it cannot hide the workflow from a key limited to part of the map. Such a key is told a draft’s id and title only when the draft is itself in its scope.
  • Field. A signal a rule raised goes to that rule’s workflows only, and a key limited to part of the map is told none when they are out of its scope. A retired playbook or a retired rule no longer routes a signal.
  • Field. list_signals with a workflow or department that does not exist, or that the key cannot see, answers an empty page at once. Ids may be written in either case. get_task_context names, as department, the first department among the workflows that have one. get_map_overview counts the policies scoped to a department or to an operation in each department’s policies.
  • Tool. build_map with files and no upload_id says to call it with op submit. Its annotations now say it is not idempotent (op submit opens a new upload on every call), and the request_action listed with op list only is annotated read-only.

No tool was added, renamed or removed, and every input is optional: a call without them answers as before.

2026-11-19: Merged tools, beside the ones they replace

Four merged forms are live beside the tools they replace, so your agent can move to fewer tool names while everything it calls today keeps working until 2027-04-30.

What changed.

  • Tool. wake_subscription is new: its op set and op remove do what set_wake_subscription and remove_wake_subscription do, for the same keys, with the same arguments.
  • Field. request_action takes op list, with status and limit, and answers as list_requests does. A key that cannot ask is listed request_action with op list only.
  • Field. build_map takes op: submit, with files, answers as submit_sources does; start is the call it always was, and a call without op is still start; status reads where an upload’s run stands and starts nothing.
  • Field. get_map_overview takes setup_check: true wherever the setup check is offered, and adds setup_check, which answers as check_setup does, also on a workspace without a map.
  • Tool. The five old tools stay listed and answer as before. Each description starts with “Replaced by” and the date it works until, and every answer carries deprecated: { use, args, remove_after }. The Migration page lists them.

No tool was removed or renamed, and no call an agent makes today changes.

2026-11-19: Workflows and departments over MCP

Your agent can now tell which workflow and department a piece of work belongs to, find and read a workflow, and count what came of the work per workflow or department.

What changed.

  • Field. get_task_context returns workflow (id, name, department) and department for a signal or a task, with workflows when several handle it. list_signals names each signal’s workflow and takes the inputs workflow and department.
  • Field. search finds workflows (workflow:<id>) and fetch reads one: its purpose, department, status, playbooks, and the rules, policies and objects derived from them. get_object has used_by_workflows; get_map_overview has departments with their counts.
  • Field. get_value_summary takes group_by (workflow or department). draft_playbook with part whole takes workflow, to put the new draft in it, and answers workflow_placed.

No tool was added, renamed or removed, and every input is optional: a call without them answers as before. A key limited to part of the map sees only the workflows whose every playbook, drafts apart, is in its scope.

2026-11-19: One alarm per removed object, with since when

A removed object that your rules, playbooks or policies still depend on now raises one alarm for its name, and says since when it has been off the map.

What changed.

  • Field. dependency_removed is one signal per object name: its dedupe_key is dependency_removed:name:<hash of the name>, and the payload has identities (every removed identity of the name; identity_id is the first) and since. Each entry of dependants lists the identities it reads. The alarms raised per identity before are answered by the first one per name.

No tool was added, renamed or removed. payload.removal, payload.cause and every other field keep their meaning.

2026-11-19: A removal waits for what depends on it

Something a live rule, watch, playbook or policy reads no longer leaves the map while they still point at it. When it left anyway, your workspace gets one alarm that names them and the ways out.

What changed.

  • Field. list_signals has a new kind, dependency_removed: one per object that a live rule, watch, playbook or policy depends on and that is no longer on the map, with the dependants, the cause and the ways out in its payload.
  • Field. A rule_broken signal of a rule that cannot be judged because the object it reads left the map carries payload.removal: how it left (kind), whether a person decided it (by), when and by whom. Its payload.cause has a new customer code, removed_by_person.

No tool was added, renamed or removed. Every existing field keeps its meaning.

2026-11-18: A rule that cannot be judged says why, by type

A rule_broken signal now carries a typed cause beside its reason, so your agent can tell a change on Maplith’s side from a change in your own data without reading the words.

What changed.

  • Field. list_signals and get_task_context: a rule_broken signal’s payload has cause, with code (for example source_stopped, column_not_in_file, reused) and party (maplith, customer or unknown). The steps on the signal are unchanged.

No tool was added or removed, and the reason and the steps on a rule_broken signal read as before.

2026-11-18: Work is one list, the chain moves to Workflows, and Rules has two tabs

Everything that needs you or your agents is one list under Work, with the same five statuses everywhere: New, Planned, In progress, Waiting on a person and Done. How your company is set up left Home: it is now the first tab of Workflows, with workflows between a department and its playbooks, and a page for each department. Rules now answers two questions in two tabs; decisions about rules are cards in place, and they are the same tasks Work lists.

What changed.

  • Page name. The tabs Waiting on me and Changes are gone. Work › List holds every task; Waiting on me is a filter at the top of it, and what needed nothing from you is a view of it. An agent’s request opens as its own task, where it is decided; the old approval link opens that task.
  • Page name. Home’s section How your company is set up is now the page The chain, in Workflows. Each department has its own page under it, with its people, systems, agents and findings.
  • Page name. Workflows › All workflows is a new page: every workflow with its department, whether it runs, needs setup or is paused, and how many of its tasks wait on a person. Each workflow has its own page, with when it starts, how it is handled, who acts, what limits it and where it works.
  • Page name. The business policies moved from Sources › Agents to Rules › Must hold, under Written here, and a policy’s page goes back there. Where business policies are on, Rules › Must hold has a filter for its two sources, Written here and the rules read from your documents, which keep their layers. What waits on you there (rules that clash, exceptions to confirm, rules that may be the same) is a card in place, and each card is the task Waiting on a person in Work › List, so a decision is made once.
  • Page name. Rules › Watch for shows each rule as one sentence, in one of six states (Working, Fired, Cannot be checked, Not checked yet, Off, Retired), grouped by department where departments are set up. A rule that reads a weak join says so, and a rule no workflow handles says "Nothing handles this yet: no workflow".

No tool or field changed in this release, and no function was removed. Every old address still opens the list, with the filter it meant. Home keeps one line that points to The chain, which appears for workspaces where departments and the systems layer are on. Every action on the Rules pages is still there.

2026-11-17: A simpler menu: seven places, in the order you use them

The menu of a workspace now follows the order in which you use Maplith: you connect sources, read the map, look at the findings, set up the workflows and rules, and do the work. Its pages were renamed to match, and the docs, the MCP’s answers and the app say the same names.

The five steps, in the order you use them:

  1. Sources. What Maplith reads and learns from. Maplith only reads your systems. It never writes to them.
  2. Map. How your company fits together: its systems, its data and how work flows.
  3. Findings. What Maplith found that does not work as your company intends.
  4. Workflows. What is set up to be handled from now on, and how. Rules. What Maplith watches for, and what must always hold.
  5. Work. What is being done, who has it, and what waits for you.

What changed.

  • Page name. Pages were renamed, regrouped or moved under the menu above. The table lists each old name beside the page that has it now.

Every page's meaning, old name included, is in Words.

Old nameIs now
OverviewHome
InboxWork
Agent workWork › List
SignalsWork › List
From your agentsWork › List
Needs youWork › List
Setup checkWork › List
ActivityWork › List
AgentsWork › List
ActionsWork › List
Map activityWork › List
ValueWork › Results
What runsWorkflows › Playbooks
AutomationsWorkflows › Playbooks
Runs outside MaplithWorkflows › Playbooks
Rules & know-howRules
RulesRules › Watch for
WatchesRules › Watch for
WatchA live rule
From your documentsRules › Must hold
DecisionsRules › Must hold
Business mapMap
SummaryMap
System mapMap › Systems
GlossaryMap › Terms
Data sourcesSources
Agents & accessSources
SystemsSources › Integrations
SourcesSources › Scans
ConnectionsSources › Agents
Agent keysSources › Agents
PermissionsSources › Agents
PoliciesSources › Agents
ActionsSources › Agents
UsageSources › Agents
Account securitySettings › You › Security and linked accounts
Members & rolesSettings › Workspace › People
Privacy & maskingSettings › Workspace › Data and privacy
Data & retentionSettings › Workspace › Data and privacy

No tool name changed in this release, and no function was removed. Every page you used is still there under its new name, and an old address forwards to it or opens it.

← All docs · Markdown version