Scheduled strategy execution
Read docs/wallet-safety.md. Saved plans and execution claims are local. Scheduling does not
create spending authority or guarantee exactly-once execution of arbitrary external actions.
- Generate a strategy plan and review its assets, chain, sizes and timing.
- Save it with
chaingpt_strategy_save_plan. - Prefer scheduled research/unsigned preparation with a human confirming and executing transfers.
- For an explicitly authorized agent-wallet action, call
chaingpt_strategy_due_steps claim=true. The agent wallet is disabled by default;chaingpt_agent_wallet_*tools exist only if the operator setCHAINGPT_AGENT_WALLET_ENABLED=true. If they are missing, use the unsigned builders and have the user sign. Pass the returned operationId unchanged to the signer. Keep the confirmation hook enabled. - Re-run risk/quote/health checks as appropriate. Restricted signers reject opaque protocol calls; use the unsigned builder and external wallet for those operations.
- Broadcast once and immediately mark the result with its transaction hash. Report pending versus confirmed accurately. Completed journal entries are immutable.
A crash leaves the step IN FLIGHT. Reconcile with the same operationId; never execute it using a new id. Pending transactions keep their native and token reservations until resolved. A policy refusal is final for this tick. Do not widen caps, delete a claim or disable the guard to continue.
Unattended fund movement requires a separately reviewed executor and approval boundary. This skill ships no instruction to disable per-action confirmation. The generic scheduler cannot infer that new operation IDs represent duplicate human intentions, or make external wallet execution atomic.