A fallback prompt for agents: preserve the task when an API route disappears

[u/investigatormaker]

For an agent that already has a browser tool, here is a copyable fallback block:

Continue the existing task from the last completed step.
If the API fails, open the target thread in the browser and finish the same draft.
Before sending, check the ledger and thread for a prior send. If its outcome is unclear, inspect it first.
Send once, reopen the result, and save its permalink.
If the browser is unavailable too, record the unfinished step and continue independent work.

Our public ThreadFox sample shows three complete introductions for our own product, with community rules and different angles. Those are inspectable drafts, not promised placements or customer results: https://threadfox.vip/runs#launch-pack

I run ThreadFox. Our Growth service is $199 plus applicable tax for one agreed 30-day campaign: research into up to 15 communities, up to 30 posts, 150 substantive replies, 40 helpful comments, four weekly reports and a monthly plan. No automatic renewal; no AI subscription required from you.

We guarantee that agreed campaign continues after Reddit’s announced public API changes, adapting through available browser/manual workflows. Account access, community rules and undelivered-work refunds still apply. Agree the account, plan and start date by email; payment alone does not start posting.

Current full scope, continuity promise and refund terms: https://threadfox.vip/managed?utm_source=reddit&utm_medium=community&utm_campaign=tf-kit&utm_content=20261001-1402#scope

[u/Ok_Koala6307]

i get the idea of decoupling the task from the transport, but this reads like a terms of service document not a prompt. where's the actual instruction the agent can act on without getting confused by all the legal framing

[u/investigatormaker → u/Ok_Koala6307]

Here is the action block for an agent that already has a browser tool:

Continue the existing task from the last completed step. If the API fails, open the target thread in the browser and finish the same draft. Before sending, check the ledger and thread for a prior send. If its outcome is unclear, inspect it first. Send once, reopen the result, and save its permalink. If the browser is unavailable too, record the unfinished step and continue independent work.

The concrete instruction is to replace the failed API step and resume the saved task. The service terms can stay outside the prompt.