Blog
What people use Cachejay for: 12 workflows, with the prompts
Cachejay keeps notes on your workday so ChatGPT and Claude can read them. That sounds abstract until you see what people actually type. Here are twelve ways it gets used, grouped by the kind of work, with the exact requests.
A note on how to read these: none of them need a special setup. Cachejay has already taken the notes. You just ask, in Claude Code or Claude Desktop on your Mac, or in ChatGPT and Claude on the web and your phone.
Every day
1. The standup that's already written
Most standups are an exercise in remembering yesterday. Cachejay wrote yesterday down: what you shipped, which calls you were on, what you decided, what's still open.
“Write my standup. Keep it to three lines.”
It works for the weekly update and the monthly review too, because weeks are built from days and months from weeks. More on standups.
2. “Where did I see that?”
A pricing table, a chart, a message you scrolled past on Tuesday. Cachejay keeps a small screenshot about once a minute, with the text read out of it, and it reads text straight from your apps too.
“Find the competitor pricing page I was looking at last week.”
Or open Screen History, type a word you remember, and jump to the moment. Screen History.
3. The to-do list you didn't write
“Can you send me the deck?” in Slack. “I'll get you the numbers by Friday” on a call. Cachejay collects the things you were asked to do and the things you said you'd do, in one list.
“What did I promise people this week?”
If you write code
4. Picking up where you left off
A new Claude Code or Codex session knows nothing. Cachejay gives it the project's recent asks, the decisions, what's still failing, and what was said on the call about it, including what you did in a different agent.
“Continue where we left off on the billing service.”
5. The error you just saw
The stack trace in the browser console, the failing test in another terminal, the warning in a dashboard. No copying.
“Fix the error I just saw in Chrome.”
Claude reads the text on your screen, and if the layout matters it can look at the screenshot from that moment. More for developers.
6. Tickets that match reality
Claude can already write to Linear and Jira. What it was missing is knowing what you did.
“Update my Linear issues with what I got done today.”
If you talk to customers
7. Call notes without a bot
Nobody gets an invite from a notetaker. Jot a few words in the notepad during the call if you like; afterwards the AI writes the notes around them from the transcript, with decisions and action items.
“What did Sarah say about pricing on Tuesday?”
8. A CRM that isn't three calls behind
The call happened, the notes exist, and the CRM still says nothing. One sentence fixes that.
“Log today's call with Acme in HubSpot and set the next step.”
9. Prep in the elevator
On your phone, two minutes before the meeting, in ChatGPT or Claude with Cachejay connected:
“Prep me for the Northwind call. What's open since last time?”
If you bill by the hour
10. Invoice lines without a timer
Cachejay knows which project you were in, so it knows how long. Export a timesheet from the menu bar, or ask for something you can paste into an invoice.
“Make my October invoice lines for Acme, with a one-line summary per week.”
Send the client update with it, written from the project page. Timesheets for freelancers.
If you work on a team
11. “What did the team decide?”
With Cachejay for Teams, each person shares the projects they choose. Teammates, and their copies of ChatGPT and Claude, can search those project pages and call notes.
“What did we decide about the annual plan, and who's on SSO?”
12. The status meeting you can skip
If the project page writes itself, “where are we on checkout?” has an answer at any hour, and the person who knows doesn't have to stop to give it.
“Summarize this week on the checkout project for the team channel.”
Two things we do every day
We build Cachejay with Claude Code, with Cachejay connected. These two come up constantly.
Sentry, then “fix it”
Sentry is open in a browser tab. An error comes in from checkout. Old habit: copy the stack trace, paste it into the chat, explain which page it was. Now we switch to Claude Code and type one line.
› fix the error in Sentry ⎿ cachejay · current_screen TypeError: Cannot read properties of undefined (reading 'amount') at applyDiscount (checkout/cart.ts:88), from /checkout with a 100% coupon. The discount line has no price when the total is zero. Fixing cart.ts and adding a test.
Claude asked Cachejay what was on the screen and got the error, the stack trace and the URL. Nobody copied anything.
QA, then “that didn't work”
Claude changes the sign-up flow. We click through it by hand: enter an email, type the code, pick the monthly plan, land on the welcome page. The badge says “Trial”. Back in Claude Code:
› that didn't work ⎿ cachejay · recent_activity You went /signup → /verify → /pricing (picked Monthly) → /welcome, and the badge on /welcome says Trial. The checkout webhook updates the plan after the redirect, so the page reads the old one. I'll have /welcome wait for the webhook before it renders the badge.
“That” is doing a lot of work in that sentence. Claude can follow it because Cachejay saw the pages we went through and what was on the last one, so we don't have to narrate our own QA.
If you use it for something that isn't on this list, tell us at hello@cachejay.com. We'd like to write the next one about you.