# Organise Codex work through projects, plans and connected tools

Follow the portions supported by the supplied recording and keep Luke’s model preference attached to his reported experience.

[HTML](https://lukejbyrne.com/library/guides/wzojy9mohn0/)
Content language: en
Author: Luke Byrne
Video published: 2026-05-10
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=wZOjy9mohn0)
Video language: English

## Choose the project before the tools

The May description presents Luke’s daily Codex workflow and his preference for GPT-5.5 over Opus 4.7. It links that preference to his reported experience, including financial information reaching the wrong recipients. That account explains his choice; it is not a controlled safety or capability benchmark for either model.

The supplied recording lasts 5:14. Its retained chapters cover the model comparison, projects and chats, plan mode, and plugins. Use those parts as the basis for a small project workflow rather than assuming the description’s later timestamps are available in this cut.

1. Choose the project folder and start a chat with a concrete task.
2. Use the projects, chats and plan-mode section at 2:10 to review how the work is organised.
3. Describe the expected output before selecting the connected services.

## Use planning to settle the next action

Luke’s description favours plan mode and extra-high reasoning. Treat those as his settings for this workflow, then review whether the proposed plan actually addresses your task. Planning is useful when it clarifies the intended change, dependencies and decisions before work proceeds.

1. Read the plan and resolve unclear requirements.
2. Confirm which files or connected sources are relevant to the job.
3. Keep the planned result available when reviewing the later output.

## Connect the tool the job needs

The plugin section at 4:03 names browser use, GitHub, Gmail and Sheets; the description also mentions image generation and the side panel. Choose tools according to the required evidence or action, not simply because a connection exists.

The original visual-resource link is PixPretty: https://bit.ly/4txAnYR; the dictation resource is idonttype.com: https://idonttype.com. The description says the video was written and packaged with Scripti: https://scripti.ai. It mentions automations and parallel chats, but the two later chapter markers lie outside this supplied recording.

1. Inspect the account or repository used by a connected tool.
2. Review the output or artifact against the original task.
3. Use the available preview or terminal evidence to check a claimed change.

## The takeaway

Keep the project, plan and connected tool aligned around one inspectable result.

## Workflow resources

- [bit.ly](https://bit.ly/4txAnYR)

## Chapters

- [00:00 GPT-5.5 vs Opus 4.7 — why I switched](https://www.youtube.com/watch?v=wZOjy9mohn0&t=0s)
- [02:10 Projects, chats, and plan mode](https://www.youtube.com/watch?v=wZOjy9mohn0&t=130s)
- [04:03 Plugins: browser, GitHub, Gmail, Sheets](https://www.youtube.com/watch?v=wZOjy9mohn0&t=243s)

## Sources and limitations

Written companion prepared 2 November 2026 from this exact published video description and its chapter sequence. The full recording was not independently watched or transcribed for this article, and the products and reported results were not retested. Checklists are editorial adaptations of the documented workflow. Model availability, interfaces, prices and offers may have changed since publication; use the retained original resources for current requirements. The published description also lists 6:49 and 9:02, both beyond the supplied 5:14 recording duration. Those markers are omitted, without retiming the retained chapters.

[Original video](https://www.youtube.com/watch?v=wZOjy9mohn0)