Claude and I agree: Actions are core to Pickaxe, but they aren’t managed like core objects.
My experience in the UI: to find and delete a custom Action, I had to go into an unrelated Pickaxe, open the flow for adding
an action, and use it as a side door to reach the action list. There is no standalone place to browse, search, edit, or delete
Actions on their own. It’s not discoverable, and it makes cleaning up test actions awkward enough that most people won’t
bother.
Claude’s experience through the MCP server: the tools cover create_manifest, update_manifest, export_manifest, and
connect/disconnect, but there is no action delete and no Pickaxe delete. Cleaning up after a test is therefore only possible
by hand in the UI. In my workspace, action_list returns about a hundred actions, including several of my own abandoned test
actions. If deleting an action is this hard, leftover clutter is the predictable result.
It’s 2026. If Actions matter enough to build a platform around, a feature should work the same way in the UI and through the
MCP:
- A standalone Actions page: list, search, edit, delete.
- action_delete and pickaxe_delete in the MCP, so scripted tests can clean up after themselves.
Context: this came up while testing the environment-variable behavior in my other thread (8870). The same gap showed up there:
the Action Editor has a value field that looks like the place to put a setting but has no effect on connections, and nothing in the MCP can read or write it.