Get your free AI plan
Docs / Migration

Migration

Which tools are being merged, the order every merge follows, how long an old name keeps answering, and what to do at each step.

What changes and why

Maplith is folding some tools into others, so an agent is listed fewer tool names: 36 now, 31 once the merges below are done, counted across all key shapes (a key is listed the tools its shape allows; see Key shapes). A tool that is folded in does not vanish at once. It is replaced in a fixed order, and the old name keeps answering for a window, so a connected agent, a playbook or a prompt that still uses it keeps working.

From the first step of a merge, the description of each old tool says which tool replaces it and the date it works until. The page is also served as markdown at /docs/md/migration and over MCP as maplith://docs/migration.

The order every merge follows

  1. Add. The merged tool, or the new op of an existing tool, goes live. The old tools stay listed and unchanged. From this step each old tool’s description starts with “Replaced by”, the tool it is replaced by and the date it works until, and its result carries deprecated: { use, remove_after }. *What you do:* Nothing breaks. Start calling the new form when your client lists it, and refresh your tool list to see it.
  2. Wait. A person confirms that ChatGPT’s scan has approved the new definitions and that they show in ChatGPT. ChatGPT keeps its own reviewed copy of each tool, and a new definition reaches its users only after that scan passes. This is a manual gate: nothing is unlisted until it is passed. *What you do:* Nothing. The old tools stay listed while the gate is open.
  3. Unlist. The old tools leave tools/list, so a client that refreshes its list no longer shows them. *What you do:* Change the playbooks, prompts and instructions you wrote to call the new form. A call to an old name still works.
  4. Keep answering. A call to an old name still works and answers as the new form does. Every call is logged with the key and the old name, so it is known who still uses one. *What you do:* Move your calls over while the window below is open.
  5. Remove. After the window below, the old name is removed. A call to it is refused with a pointer to the tool that does the job now. *What you do:* Nothing, if you have moved over. A call to a removed name gets the pointer, and nothing is computed.

The window

An old name answers for 90 days after it is unlisted, and it is not removed before 30 days with no calls. Before a removal, an admin whose keys still call the old name will get one task in Work, 30 days ahead.

Merges in progress

Each row is one old tool and where it goes. A status of Planned means the merged form is not added yet: nothing has changed for you. When a merge reaches its first step, the status becomes “Replaced by” the new tool and the date the old one works until.

Old toolBecomesStatusWhat to do
submit_sourcesbuild_map with op: submitReplaced by build_map until 2027-04-30Call build_map with op: submit from now on. submit_sources works until 2027-04-30.
list_requestsrequest_action with op: listReplaced by request_action until 2027-04-30Call request_action with op: list from now on. list_requests works until 2027-04-30.
check_setupa section of get_map_overviewReplaced by get_map_overview until 2027-04-30Call get_map_overview for the section from now on. check_setup works until 2027-04-30.
set_wake_subscriptionwake_subscription with op: setReplaced by wake_subscription until 2027-04-30Call wake_subscription with op: set from now on. set_wake_subscription works until 2027-04-30.
remove_wake_subscriptionwake_subscription with op: removeReplaced by wake_subscription until 2027-04-30Call wake_subscription with op: remove from now on. remove_wake_subscription works until 2027-04-30.

redeem_action_grant is not merged with the others. A grant is single-use, signed and checked again when it is spent, and the reference executor calls the tool by name, so it keeps its own name and its own place among the tools.

Names that already changed

These names changed in earlier releases. They are not listed any more, and an agent that holds an older tool list or an instruction that names one still gets an answer. Its row says how it answers: a renamed one runs the tool in the second column and adds renamed_to to the answer; a removed one is refused, and the refusal says where the job lives now. No date is set for removing them: a name that is still called is not removed before 30 days have passed with no calls.

Old nameHow it answersUse insteadWhat to do
answer_field_identityRuns answer_question, as beforeanswer_questionCall answer_question with kind: field_identity. answer_field_identity runs it for you for now.
answer_grainRuns answer_question, as beforeanswer_questionCall answer_question with kind: grain. answer_grain runs it for you for now.
answer_schema_dialectRuns answer_question, as beforeanswer_questionCall answer_question with kind: schema_dialect. answer_schema_dialect runs it for you for now.
answer_lineage_directionRuns answer_question, as beforeanswer_questionCall answer_question with kind: lineage_direction. answer_lineage_direction runs it for you for now.
list_processesRuns get_process, as beforeget_processCall get_process without an object_type. list_processes runs it for you for now.
list_metricsRuns get_metric, as beforeget_metricCall get_metric without a name. list_metrics runs it for you for now.
list_watchesRuns get_rule, as beforeget_ruleCall get_rule without a rule_id. list_watches runs it for you for now.
get_watchRuns get_rule, as beforeget_ruleCall get_rule with the arguments you sent. get_watch runs it for you for now.
flag_joinRuns join_review, as beforejoin_reviewCall join_review with op: flag. flag_join runs it for you for now.
report_join_checkRuns join_review, as beforejoin_reviewCall join_review with op: report. report_join_check runs it for you for now.
propose_playbookRuns draft_playbook, as beforedraft_playbookCall draft_playbook with part: whole. propose_playbook runs it for you for now.
draft_playbook_stepsRuns draft_playbook, as beforedraft_playbookCall draft_playbook with part: steps. draft_playbook_steps runs it for you for now.
withdraw_requestRuns request_action, as beforerequest_actionCall request_action with op: withdraw. withdraw_request runs it for you for now.
estimate_scanRefused, with a pointer to get_map_overviewget_map_overviewCall get_map_overview: for a workspace without a map its first_map carries limits and budget_today; with one, submit_sources answers with the share its upload takes.
record_dmarc_rungRefused, with a pointer to record_actionrecord_actionNothing to record here: after your human changes DNS, the email domain check records the stricter policy on its next run. Record what you did with record_action.
list_stated_relationshipsRefused, with a pointer to get_map_overviewget_map_overviewCall get_map_overview and read stated; for one object, get_object.
list_wake_subscriptionsRefused, with a pointer to get_map_overviewget_map_overviewCall get_map_overview and read your_key.wake_ups.
send_test_wakeRefused, with a pointer to set_wake_subscriptionset_wake_subscriptionCall set_wake_subscription with the endpoint’s id and test: true (an autonomous key); otherwise your human sends a test from Sources › Agents.

Pages

The names of the app’s pages changed as well. The old names are in Words, in the last column, with what each page was called before. An old address forwards to the new page or opens it, so a link you saved still opens the right page.

Where to go next

  • Changelog: what each release changed, newest first.
  • The MCP reference: every tool as it is now, with its status.
  • Words: what each name means, and what it was called before.

← All docs · Markdown version