# Run preparation on a schedule

> The app stores due work; your external client must actually pick it up.

Canonical: https://ownpost.fyi/docs/guides/agent-runner

## Before you begin

A working AI connection.

## Steps

1. Use the preparation request for post drafts.

2. For preparation, use Assistant → Copy preparation request.

3. Run the chosen prompt once in your connected client. Check the returned result and the last recorded run/check-in in the app.

4. Create a schedule supported by your client using that prompt. Saving an interval inside OwnPost does not create this external schedule.

5. Keep a local runner's computer, client and connection available. Verify a later real check-in rather than assuming the schedule is active.

6. If work waits, copy/run the request manually or repair the external schedule. Keep unchanged/no-work runs quiet.

## Example request

Run one due preparation request by hand and inspect the saved drafts before placing that same request in your client’s scheduler. A successful later check-in is the evidence that the runner works unattended.

```
Use the ownpost-run-assistant skill to complete one due OwnPost preparation job. Follow its saved brief and save the results. If there is no work, stay quiet.
```

## Check the result

A due preparation request completes and its result appears in Assistant.

## Troubleshooting

No check-in means no verified runner activity. A saved connection or copied prompt is not a scheduler.

## Keep going

[Connect your assistant](https://ownpost.fyi/docs/guides/connect-ai)

[Build your daily writing challenge and routines](https://ownpost.fyi/docs/guides/routines)

[Claude Code MCP configuration](https://code.claude.com/docs/en/mcp)

## Related

- [Previous: Conversational setup](https://ownpost.fyi/docs/guides/guided-setup)
- [Next: Personal preferences](https://ownpost.fyi/docs/guides/personal-preferences)