Original video in Chinese.
Key Takeaways
- The sidebar provides files, a browser, and a terminal, making Codex an environment that sits alongside the work itself.
- Open a local knowledge-base folder, read and edit documents on the right, and discuss the project with Codex on the left. Direct edits reduce app switching and repeated copying.
- I use the browser for Perplexity research and the terminal for other tools such as newtype OS. Codex can read terminal output as live context even when it cannot directly operate that built-in terminal.
Many people overlook the Codex sidebar, but I find it extremely useful. Open it and you will see three options: files, browser, and terminal.
Files: work on documents together
If you create content or frequently read and revise documents while working with AI, the file view is especially useful.
Create a project in the left sidebar based on an existing folder, such as your knowledge base. Open Files on the right to see the full folder structure. Documents are readable and editable there.
The interface now has two halves. On the left, you discuss the project and its knowledge base with AI. On the right, you see documents being created or changed.
When I dislike something AI has written and do not want another round of discussion, I can edit it directly. This is how I most often collaborate with Codex: we share a workspace and the same context.
Browser: bring research into the project
My most frequent use is Perplexity. Codex can search online, but I prefer Perplexity for research. In my experience, its search quality, particularly Perplexity Computer’s depth and output, is strong.
If a result is valuable, I ask Perplexity to organize it as Markdown and put it into my knowledge base or give it directly to Codex.
You can also open YouTube while waiting for Codex to complete a task.
Terminal: use other tools alongside Codex
You do not have to use Codex alone. Open another CLI, such as Claude Code, in the terminal if that fits your workflow.
I most often use newtype OS, which I built for content production. With its memory system and Wiki, it understands my material and style, so I handle almost all my content work there.
In the setup described here, Codex could not directly operate the built-in terminal, but it could read terminal output as real-time context. That creates useful possibilities to explore.
With files, browser, and terminal together, the things I need are in one workspace and can cooperate with Codex. I can avoid continually switching applications.
These three tools are familiar individually. Their value comes from bringing AI closer to the work: it can stay beside your project instead of waiting for copied fragments.
That is what I appreciate about Codex. It is a workspace you can adapt. Add your knowledge base, open the browser, connect the terminal, and make AI part of your own working system. The change is small, but its direction matters.
That is all for this episode. If you want to understand AI, reclaim personal sovereignty, and meet people with similar interests, join the newtype community. See you next time.