The prompt that finally got Claude Code to do the right thing is worth keeping. The problem is where it lives: thousands of lines deep in a terminal you will close tonight. This guide covers how to save your favorite prompts from Claude Code and Codex so you can find and reuse them later, instead of rewriting them from memory every time.
The short answer
Share the session to Lore with /share, open the thread in your browser, and star the individual prompts worth keeping. Your starred prompts collect on the /favorites page under the Prompts tab, newest first, so the prompt that worked is one click away the next time you need it.
Why saving prompts matters now
A year ago, the valuable artifact of a coding session was the code. Now it is often the prompt. A well-shaped prompt, the one that framed the problem correctly, set the constraints, and got a clean result, is reusable across projects and worth more than the specific diff it produced once.
But prompts are ephemeral by default. They scroll past, the terminal closes, and the next time you face the same task you start from scratch. Saving the good ones turns a one-time win into a reusable asset.
How to save a prompt with Lore
There are two levels: saving a whole session, and saving the specific prompts inside it.
Save the session. Run /share inside a Claude Code or Cowork session, or /share-codex inside a Codex session. The thread exports to Lore and you get a URL where the whole conversation renders in your browser.
Star the prompts. Open the thread. Each of your prompts has a star button (it appears when you hover over the prompt). Click it to favorite that individual prompt. You can also star the whole thread from its header if the entire session is worth keeping.
Find them later. Go to the /favorites page. It has two tabs: Threads and Prompts. The Prompts tab lists every prompt you have starred, so your best prompts become a library you can scan instead of scrollback you have to dig through.
Saving a whole thread vs. a single prompt
Use the right grain for what you are keeping.
- Star a single prompt when one specific instruction is the reusable part, for example a prompt that reliably gets a clean refactor, or one that frames a migration the right way. You want that exact wording later.
- Star the whole thread when the value is the full session: the sequence of steps, the dead ends, and the reasoning that got to the answer. You want to re-read the whole thing.
Most people end up using both: a handful of starred threads for "how we solved this," and a growing set of starred prompts for "the wording that works."
Make it a team asset
A saved prompt is more useful when your team can see it. If you set a shared thread's visibility to workspace, teammates can open it, read the prompts that worked, and reuse them. Over time, the prompts your strongest engineers rely on become visible to everyone instead of staying locked in one person's terminal history.
Frequently asked questions
Can I save individual prompts, or only whole sessions?
Both. In Lore you can star an individual prompt inside a thread, or star the entire thread. Starred prompts and starred threads each get their own tab on the /favorites page.
Where do my saved prompts go?
To your /favorites page, under the Prompts tab, listed newest first. Starred threads appear under the Threads tab. Your favorites are private to you unless the underlying thread is shared with your workspace or made public.
How do I save a prompt from Codex instead of Claude Code?
Share the Codex session with /share-codex, open the resulting thread in Lore, and star the prompts the same way you would for a Claude Code session. Once exported, Claude Code and Codex threads behave identically.
Do I need a paid plan to save prompts?
No. Favoriting prompts and threads works on the free tier. Note that on the free tier, shared links expire after 3 days; the Team plan ($20/seat per month) keeps links permanent, which matters if you want a saved prompt to stay reachable long-term. Pricing is current as of June 2026.
Is this the same as prompt versioning tools?
No. Prompt versioning tools manage the prompt templates your application sends to an LLM API at runtime. Saving favorite prompts in Lore is about the prompts you personally write when coding with an agent, so you can find and reuse them. Different problem, different tool.
A practical starter
Next time a prompt works unusually well, do not just move on. Share the session, star that prompt, and add one note about why it worked. After a few weeks you will have a personal library of the wordings that reliably get good results, which is far more valuable than any single diff they produced.