Let AI Be Your Mentor: A Self-Review Routine with Claude Code /insights and Codex Computer History

If you use both Claude and Codex and have Computer History turned on, two small tricks go a long way: ask Codex to act as your mentor and review your recent work using Computer History, then run /insights in Claude Code to get a review report that moves from the big picture to the small details, so you end up with a summary for steady growth.

2026/10/13 · 3 min read

On the left, a monitor filled with a whole day's work activity; in the middle, a magnifying glass examining a session log; both feed into a report on the right with a growth chart and a checklist, drawn as an engineering blueprint

If you use both Claude and Codex, and you have Codex's Computer History turned on, these two small tricks go a long way.

Every day we write code, open PRs and fix bugs alongside AI, and we get a lot done, but we rarely stop to look at how we're actually doing. Which habits are slowing me down? Where do I keep stepping into the same pothole? On these questions, the AI's records are actually more complete than my own memory.

So here is what I do: I let AI be my mentor.

Trick 1: Ask Codex to review my recent work with Computer History

Computer History turns your work trail on your computer into memory that Codex can use in later conversations. Once it's on, @ it in Codex and ask it directly to be your mentor:

@Computer History Please act as my mentor, review my recent performance, and give me related advice.

It looks at the working context across your whole computer, not just one repo or one conversation, so its feedback leans toward the big picture: where your time goes, whether you switch tasks too often, and which things keep getting put off.

Trick 2: Use /insights in Claude Code for a review and suggestions

In Claude Code, enter:

/insights

It analyzes your recent Claude Code sessions and produces a review report: your work patterns, what you're doing well, where you get stuck, and concrete suggestions for improvement.

Two extra tips:

Once the report is out, you can simply tell Claude to translate it into your native language, which makes it much faster to read.
Also check the "Reflection" section in the web version's settings and compare it with the report.

From the big picture to the small details

The two tricks complement each other:

Computer History: looks at your work trail across the whole computer and evaluates the big picture.
/insights: looks at every Claude Code session and reviews the details.

Put together, everything from the big picture to the small details gets a chance to be summarized and analyzed, giving you a summary and a full report that help you keep growing.

A reminder

Computer History records what you do on your computer. When you're handling customer data, account passwords or other sensitive content, remember to pause recording first, or use the settings to exclude those apps and websites. It works great as a mentor, but you have to keep an eye on what gets recorded.