Selecting a long response to copy repeatedly is kinda tedious as I use Codex CLI for a long time. Particularly for long responses.
Out of curiosity, why are you needing to copy out of Codex CLI so often?
What do you usually copy, the very final, turn-complete statement?
For example, I have a large repo and I ask Codex to audit the usage of certain APIs and I get a long report. Then I copy that report and use ChatGPT to convert into a document in a particular format. That is just one of the use cases. Most of the times, I ask Codex to implement something, copy the implementation report and run it by ChatGPT for validation. My workflow has been: I am the architect. ChatGPT is the designer and the prompt creator for Codex. Codex is the workhorse to implement based on those prompts. ChatGPT verifies the implementation report and I manually test as needed.
You don’t need to wait for OpenAI here. I just implemented this in Codexometer’s Session command centre.
As part of Codexometer’s ability to manage Codex sessions in one place it sees all text across all Codex sessions (ie including those running in a session of Codex CLI) and outputs it to each of its detail panes.
Adding the ability to Copy the final output text was a no-brainer. That is done and in the latest release. You can use a hotkey or click it with a mouse.
Feel free to try it out and let me know if that fulfils your needs or if you have any feedback.
Codexometer is quick and easy to install, free and open source.
Thanks for the idea!
Released [v0.17.4 with highlights and upgrade instructions](https://github.com/merefield/codexometer/releases/tag/v0.17.4).
- PR #58 merged after all CI passed.
- All six platform binaries and checksums published.
- Local binary matches **0.17.4**.
- Working tree is clean.
Cool, I will give it a shot.