Find any session again
Every chat is named after what you asked, filed under its project and searchable by what was said. Reopen last month's and carry on.
For coders
Thirty coding sessions. Nothing lost, nothing explained twice.
You run Claude Code and Codex in ten terminals and lose track of which one did what. Salana puts every session in a workbench, sorts it by project, keeps it forever, and lets you continue any chat in another model with the full history.
What changes
Switch models without starting over
Stuck in Claude? Continue the same chat in Codex with the full history. Or let the two debate a design until both accept.
Know which agent needs you
Leave ten agents working. Anything waiting for your answer lands in Needs you.
The why next to the code
Your repo sits next to your business context: the customer request, the decision, the spec. The agent reads both.
Four layouts, one key
Ctrl+T cycles the layout of a space. Press an icon to see it.
Dwindle: each new tile splits the last one.
Change model mid-chat
Start in Claude. Switch model and Codex continues the same chat with the full history. Switch back the same way. The chat and the task it opened stay one thing in your memory.
ClaudeDiscount logic out of checkoutContinue in Codex
Move the discount logic out of checkout into a shared helper. Keep the tests green.
Claude Extracted
computeDiscount() into lib/pricing.ts, updated the three call sites. 14 tests pass. Card TASK-0412 opened.Continued in Codex · same chat, full history
Codex Continuing from the helper Claude extracted: added edge-case tests for stacked codes and a changelog line. Closing TASK-0412 with the outcome.
what's next?
Claudewrites V2
Codexobjects, writes V3
Claudeaccepts
Codexaccepts
V3 is the document
Teach it once. Build on it every time.
Your memory, your routines, any model.