Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

In the previous post, we saw how GitHub Copilot CLI stores your prompt history locally in a file called command-history-state.json.

But did you know Copilot CLI can actually read that history and help you become a better prompter?

Meet the /chronicle slash command!

What is /chronicle?

• /chronicle is a built-in slash command that analyses your past session history and generates useful insights — all from data stored locally on your machine.

It has four sub-commands:

How to use it?

Note: /chronicle is currently an experimental feature. Enable it first by running:

/experimental on

Then run:

/chronicle tips

Copilot CLI will query your local session data — your recent sessions, message patterns, and tool usage — and generate personalised tips based on how you have been working.

When should you use these features?

• To continue previous work: Use copilot --continue or copilot --resume to pick up where you left off.
• At the start of your day: Run /chronicle standup last 3 days to generate a reminder of what you worked on recently and the CLI session you were working in.
• Periodically, to level up: Run /chronicle tips every week or two to discover features and workflow improvements you might be missing.
• When Copilot keeps making the same mistake: Run /chronicle improve to identify the pattern and generate custom instructions to fix it.
• To recall past work: Ask a free-form question like “Have I worked on anything related to the payments API?” and Copilot will search your history.

Hope this was helpful! 🙂