Get help
Contact support@pcaffinity.com for CodexContinue support or privacy requests. The developer is CloudD901.
Include the plugin version, operating system, a description of the issue, and any relevant error message. Redact secrets, account credentials, private prompts, project paths, and unrelated source code before sending logs. There is no guaranteed response time.
Check the saved schedule
After requesting a continuation, check the chat, project, date, time, and time zone in the confirmation. When you provide a custom message, check that the saved prompt matches it. “This chat” means the conversation receiving your scheduling request.
Ask CodexContinue to review your scheduled continuations if you need to inspect a schedule. Do not create a second task to compensate for an uncertain result until you have checked the existing task and chat.
Cancel or change a continuation
Cancel the scheduled continuation for this chat.
If more than one schedule matches, identify the intended one by its name or time. You can also use the app’s schedule controls to pause or remove it. Verify that it is no longer active.
To reschedule, specify the new time and any new message. Cancelling prevents future dispatch; it does not stop or undo a turn that has already started.
If it does not run
- Check that the computer was awake, Codex was running, and the project was accessible.
- Confirm that the schedule was active and used the intended local time zone.
- Check account usage and whether a required approval or sign-in prevented execution.
- If host scheduling or usage tools are unavailable, the plugin cannot create those capabilities. Use a compatible Codex desktop environment.
- If the reset time is unavailable, supply a known future time rather than assuming a reset occurred.
A schedule records an intended dispatch time, not a promise of successful execution.
Optional CLI diagnostics and cleanup
Copy the bundled scripts together to a stable directory you control before registering a Windows task. The user must remain signed in; wake behavior depends on Windows power policy. The CLI must be installed, signed in, and on your PATH.
Look next to those copied scripts for requests/ and runs/<runId>/. Run files include status.json, events.jsonl, stderr.log, and last-message.txt. These may contain private project content.
A dispatch.claim file prevents automatic duplicate prompts after uncertain failures. Investigate whether work started before retrying. Do not simply delete the claim and dispatch again.
Remove an unwanted Windows task through Task Scheduler or Unregister-ScheduledTask -TaskName '<your-task-name>' -Confirm:$false. Remove local request/log files when no longer needed. Removing a task or uninstalling the plugin does not automatically delete those files.