A full history
Go back to any file, at any point in time.
See exactly how a file looked last week or last month, and what changed along the way. Nothing gets lost.
Flowspelt · A memory for software projects
Your software has a history.Stop losing it.
Flowspelt remembers the work behind your software — what changed, when, and why — so your team and your AI coding assistants never have to start from scratch.
flowspeltbilling-apiRecordingGLOBAL
Dashboard
BILLING-API
Screen
Sessions142
Journals
Memories & ADRs
AI Chat
Knowledge Graph
Data & Storage
Sessions / Tue · 14:02 – 14:51
Fix customers being logged out
49 min4 files+50 −7 lines
FILEADDEDREMOVED
src/auth/refresh.ts+14−3
test/auth/refresh.test.ts+28−0
src/auth/jwt.ts+6−2
src/middleware/session.ts+2−2
src/auth/refresh.tschanges in this session
export async function refreshIfNeeded(token: string) { const payload = decode(token)- if (Date.now() / 1000 < payload.exp - SKEW) return token+ if (!payload?.exp) return forceRefresh(token)+ if (Date.now() / 1000 < payload.exp - SKEW) return token return forceRefresh(token)
ACTIVITY
- Session started
- refresh.ts
- refresh.test.ts
- jwt.ts
- session.ts
- Session ended
AI SUMMARY
Customers with older accounts were being logged out unexpectedly. This session fixed the login check for those accounts and added tests so the problem doesn't come back.AI ASSISTANT → FLOWSPELT
ASKSHas this logout problem happened before?
- found
- Fix for customers being logged out
- when
- 3 weeks ago · 49 minutes of work
- changed
- 4 files
The problem
Code shows what was built. It never says why.
When a developer solves a problem, the story behind it lives in their head — and fades. Weeks later, nobody remembers what was tried, what failed, or why it was done that way. New teammates start from zero, and AI assistants guess. Teams end up paying for the same work twice.
WHAT THE CODE SHOWS
if (!account.expires) renewLogin()Changed 3 weeks ago · “fix logouts”
WHAT IT DOESN’T
How long it took to get right
What was tried before it worked
Which other parts were involved
Why it was done this way
Flowspelt keeps the part the code leaves out.
How it works
It works in the background. You just get the memory.
- 01 · NOTICE
It quietly follows the work
Choose your projects once. From then on, Flowspelt notices as files change — no buttons to press, no notes to write.
Set up once, then forget it
- 02 · ORGANISE
It turns activity into a story
Changes become clear work sessions and daily summaries, written in plain language that anyone on the team can read.
Readable in a minute
- 03 · REMEMBER
It keeps that story safe
Your project history builds up over weeks and months, kept on your own computer instead of in someone else’s cloud.
Stays on your device
- 04 · ANSWER
It answers when you ask
Look things up yourself, or let your AI coding assistant check the history before it changes anything.
Works with popular AI assistants
What you get
Everything that happened, kept where you and your AI assistants can find it.
Your day at a glance
See what got done, without asking.
Work is grouped into sessions with plain titles, so anyone — developer or not — can follow progress.
Lessons that stick
Remember how a problem was solved.
When something breaks again, see what was done last time and why — instead of solving it from scratch.
A memory for your AI assistant
Your AI assistant checks the history before it guesses.
AI coding assistants forget everything between conversations. Flowspelt gives them your project’s memory, so they can ask questions like these:
- “Has this problem happened before?”Shows how it was fixed last time.
- “Why was this built this way?”Finds the decision and the reasoning.
- “What changed in this file recently?”Lists the work that touched it.
- “What did we do yesterday?”Summarises the day’s sessions.
Connects through MCP, the open standard supported by popular AI coding tools.
Also in the app
- Daily journals. A short written summary of each day’s work — useful for stand-ups, handovers and client updates.
- Ask in plain language. Type a question about your project and get an answer from its history.
- Knowledge map. See how parts of the project, work sessions and decisions connect.
- Every project in one place. Follow several projects at once and switch between them.
An example
The same problem, three weeks later. This time, nobody starts from zero.
- 01
A problem comes back
Some customers are being logged out again. A developer asks their AI assistant to fix it.
- 02
The assistant checks the history first
Instead of guessing, it asks Flowspelt whether this has happened before.
- 03
It finds the earlier fix
Flowspelt shows what was changed last time — and keeps the facts separate from the AI’s explanation.
- 04
The fix follows the known path
The assistant applies the same fix and points to the earlier work, so the team can check it.
EXAMPLE CONVERSATIONRecordedAI explains
DEVELOPER
Some customers are getting logged out of the billing page again. Can you fix it?
ASKING FLOWSPELTHas this logout problem happened before?
RECORDEDThree weeks ago, a 49-minute work session changed the login files and added tests.
RECORDEDThe same session also changed how older accounts are checked.
AI EXPLAINSOlder accounts were missing an expiry date, which logged those customers out. The earlier fix handles them.
AI ASSISTANT
This matches a problem fixed three weeks ago. The new billing page skips that fix — I'll apply the same one there and link the earlier work for review.
Is it for you?
If people write code for you, their work deserves a memory.
For companies
Software teams of any size
- New hires get up to speed from the project’s own history, not by interrupting colleagues.
- Knowledge stays when someone leaves or moves to another project.
- Managers see what got done each day without extra status meetings.
- The same problems stop being solved twice.
For individuals
Freelancers and solo developers
- Pick up any project exactly where you left off, even months later.
- Turn your day into a clear summary for clients or invoices.
- Juggle several projects without losing track of any of them.
- Your work history stays private, on your own computer.
For AI-assisted teams
Anyone coding with AI assistants
- Your assistant stops forgetting everything between conversations.
- It checks how something was done before changing it.
- Fewer repeated mistakes and fewer wrong guesses.
- Works with the AI coding tools you already use.
Probably not for you if
- You rarely write or change code.
- Your projects are small, short-lived and never revisited.
- You already keep detailed notes on every change — and actually read them.
Privacy and control
Your history lives on your computer. Here is exactly when anything leaves it.
| What | Where it lives | When it leaves your device |
|---|---|---|
| Your project history | Where it livesOn your computer | When it leavesFlowspelt doesn’t upload it anywhere. It only leaves your computer in the two cases below. |
| AI summaries and answers | Where it livesThe AI you choose | When it leavesPick an AI that runs on your own computer and nothing leaves it. Or connect a cloud AI service you trust: only what a request needs is sent, and things like passwords and personal details are automatically masked first. |
| Questions from your AI assistant | Where it livesThe assistant you connect | When it leavesAnswers go to the assistant you connected — and to whichever AI service that assistant uses. |
| Your account | Where it livesSign-in | When it leavesUsed to check your plan. Your project history is not part of it. |
You stay in control
- Pause any projectStop following a project at any time without losing its history.
- Delete what you no longer needSee what a project’s history takes up, and remove it whenever you like.
- AI is optionalHistory, sessions and timelines work without any AI at all.
Keep the context behind your software.
Flowspelt is in early access. Leave your email and we'll send you a build.