# Use Codex Goals for a bounded coding objective Enable the recorded CLI feature, give it a verifiable finish line and inspect the result after a longer session. [HTML](https://lukejbyrne.com/library/guides/xivm9za3vmw/) Content language: en Author: Luke Byrne Video published: 2026-05-06 Guide published: 2026-11-02 [Watch the video](https://www.youtube.com/watch?v=XIVm9ZA3vmw) Video language: English ## Choose work with a clear end state The May video explains Codex Goals as a way to continue toward one objective across multiple tasks. Its CLI-only statement describes that recording. The title’s 15 hours is not a guarantee of runtime or completion, and longer activity is useful only when it produces a checked result. 1. Choose one coding objective with an observable outcome, such as completing a defined feature and its relevant checks. State the files or behaviour in scope and the evidence required at completion. 2. Set a practical work limit and identify decisions that require you. Use an ordinary short task when the job is a small edit that does not need sustained iteration. ## Enable the feature and use its controls The setup chapter at 1:03 shows enabling Goals in config.toml, with confirmation at 1:48. The description supplies command names but not the exact configuration entry. Follow the recorded setup alongside the installed CLI’s supported options. 1. Open the demonstrated config.toml setup and confirm the feature is enabled before assigning the objective. Start the goal with /goal and keep the finish criteria visible in the request. 2. Use /goal pause to pause the work, /goal resume to continue and /goal clear to clear the goal when appropriate. Check the resulting state rather than assuming typing a command changed it. ## Review progress across context compaction The video discusses non-blocking work, token limits and context compaction. A continued session still needs a durable account of what changed and what remains. Compaction is part of managing conversation context; it does not itself prove the application is correct. 1. Keep decisions, completed checks and unresolved failures in project files that the next stage can read. Inspect the saved code and test evidence when the session reports progress. 2. At the finish, run through the intended user behaviour and review the actual changes against the original objective. Record incomplete parts even if the goal spent a long time working. ## The takeaway Judge the goal by the finished behaviour and supporting checks. Runtime and a continuing session are context, not substitutes for completion. ## Workflow resources - [scrimba.com](https://scrimba.com/?via=ai-luke) ## Chapters - [0:00 Codex Goals are here](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=0s) - [0:38 What Goals does](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=38s) - [0:55 CLI-only for now](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=55s) - [1:03 How to enable Goals in config.toml](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=63s) - [1:48 How to confirm Goals is enabled](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=108s) - [2:13 Main /goal commands](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=133s) - [3:25 Goals are non-blocking](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=205s) - [3:41 Two ways to use AI coding agents](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=221s) - [4:45 How to write better Goals](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=285s) - [5:13 Why Goals are different from normal prompting](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=313s) - [5:42 What happens when tokens run out](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=342s) - [6:15 Context compaction explained](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=375s) - [8:01 Practical examples of good Goals](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=481s) - [8:42 When not to use Goals](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=522s) - [9:26 Final thoughts](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=566s) - [9:36 Does longer runtime feel more valuable?](https://www.youtube.com/watch?v=XIVm9ZA3vmw&t=576s) ## Sources and limitations Prepared 2 November 2026 from the published video description and chapters. The actions are editorial follow-along guidance. The full video was not independently watched or transcribed and no new product test was run. Setup, availability and offers may have changed since the recording. [Original video](https://www.youtube.com/watch?v=XIVm9ZA3vmw)