Harnesses
Supported schedulers and the constraints to check before syncing.
| Harness | How it is reached | What to know |
|---|---|---|
| T3 Code | Local server RPC with a five-minute token from t3 auth | T3 intervals have no fixed time of day. Give an interval task a fixed time first. |
| Codex app | automation.toml files under the Codex home | The app keeps live schedules in its database and treats files as a mirror. Restart after a push and check the Scheduled page before relying on a run. |
| Claude Desktop | A SKILL.md per task plus the app's manifest | Close the app before pushing because it rewrites the manifest from memory. New tasks use the app's default permission mode, so the first run may wait for approvals in the sidebar. |
| Pi | agents-cron task list in .agents/cron/tasks.json | Pi has no scheduler of its own. A cron entry must call agents-cron run-due in the repository. |
Only schedules that fit the shared file format can be pulled. Unsupported tasks are reported and skipped. The adapters exist because no harness reads .agents/schedules/ directly yet.