← All Borrowed Recipes

Recipe notebook icon

Borrowed Recipe

A fortnightly audit of how you work, not what shipped

⁠ · ~2 min read

Stop only checking what the agent shipped.

Nikunj Kothari runs Claude Code’s /insights every two weeks to find ways to improve his setup. Thanks to Nikunj for sharing the fortnightly habit, alongside his X bookmarks.

🧾 What’s cooking

  • Why: he says /insights and /playground “seem relatively less used,” despite being his two favorites.
  • The habit: a regular cron job runs insights every two weeks and, in his words, “tells me all the best ways to upgrade my setup.” He pairs it with X bookmarks.
  • The command: Claude Code’s built-in /insights analyzes recent sessions on this machine and writes an HTML report about projects, friction and features to try (Claude Code docs).

👩‍🍳 The method he shared

  1. Run insights on a recurring two-week cadence. Nikunj says he uses a regular cron job, but the exact scheduling implementation wasn’t disclosed.
  2. Use the analysis to find ways to upgrade the setup. The post does not list the changes he made.
  3. Pair the habit with X bookmarks. He mentions this pairing without explaining the bookmark workflow.

That is the extent of the shared recipe, not a complete scheduling tutorial. He also names /playground as a favorite, but does not describe a playground workflow in this post.

😋 What the report gives you

The official docs describe an HTML report at ~/.claude/usage-data/report.html, with timestamped copies in the same folder. It covers recent local sessions, including where work gets stuck and features to try (Claude Code docs on usage patterns).

These details explain /insights; they do not establish how Nikunj’s cron invokes it.

🔥 Watch the stove

  • /insights is not available in cloud sessions. Sessions from other devices and claude.ai are not included (commands and usage-pattern docs).
  • Each run analyzes up to 200 previously unseen sessions, skips very short ones and counts against plan or API usage (usage-pattern docs).
  • The scheduling setup and unattended execution have not been tested here. Without the author’s implementation, this recipe cannot provide a reproducible timer setup.

📎 Where this came from