chieflab_approve_action
[chieflab_* alias of chiefmo_approve_action] Approve one ChiefMO publish/send action so its executor can fire. USE WHEN the user — in IDE chat — said 'approve ' (e.g. 'approve linkedin', 'approve hn'), 'approve all', 'ship it', 'go ahead', or otherwise greenlit a specific draft you rendered. Match the user's words to the channel, look up agentGuide.renderInChat[channel].actionId from the launch response, and call this tool with that actionId. This is the IDE-native approval path — no need to push the user to the reviewUrl. Pass actionId (preferred) or id (legacy alias). P74: pass autoExecute: true AND the connector inputs (platforms for social / recipients + subject for email) to have the approval chain directly into execution — approve and ship in one tool call. Without autoExecute (or when connector is manual_handoff / blocked), the response includes executionPlan and the caller is expected to invoke the suggestedTool next.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "chieflab_approve_action"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Legacy alias for actionId. | |
| subject | No | P74. For autoExecute on email: subject line override. | |
| actionId | No | The action id from publishActions[].id in a launch_product response. Preferred. | |
| mediaUrls | No | P74. Optional media URLs for the social post — auto-uploaded to Zernio's CDN before publishing. | |
| platforms | No | P74. For autoExecute on social channels: Zernio platform descriptors, e.g. [{platform: 'linkedin', accountId: '<id>'}]. Required when autoExecute=true and mode=oauth_connector. | |
| recipients | No | P74. For autoExecute on email: recipient email addresses. | |
| autoExecute | No | P74. When true AND the action's executionMatrix.mode is oauth_connector / api_key_connector / native_api AND the connector is ready, the approve handler immediately invokes chieflab_execute_approved_action with the inputs you supply. The response includes the executor result + the unified proof ledger. Defaults to false (preserves the prior contract — agent calls execute_approved_action explicitly). |