Wie du eine alte Claude Code-Session in osFoundry findest und fortsetzt
Am Ende ist eine Claude Code-Session von letzter Woche wieder auf dem Bildschirm: Du findest sie in osFoundry , indem du ein Wort aus dem Projekt eintippst, liest nach, was sie gemacht hat, und startest mit einem Klick claude --resume <id> in dem Ordner, in dem sie gearbeitet hat. Dieselbe Liste enthält deine Codex-Sessions und die von zehn weiteren KI-Apps auf dem Rechner. osFoundry spricht nie…
To resume a past Claude Code session in osFoundry, first locate it by typing a keyword from the project in osFoundry and reading about what it did. Start the session by clicking "claude --resume id" in the folder where the work was done. The osFoundry list includes your Claude Code sessions and those of ten other AI apps on the computer. osFoundry reads files but never communicates with Claude Code.
It operates in the desktop app because it reads local files, not via a login or token. The app reads session files located at ~/.claude/projects/…/id.jsonl and ~/.codex/sessions/…/. Sessions are listed and show the recorded folder, branch, model, and permission mode. After resuming, each tool call is executed with the app's own permission queries, and a CLI runs in a terminal window within the session folder.
The session ID builds the resume command, whether it's claude --resume id or codex resume id. osFoundry knows twelve apps, including Claude Code, Codex CLI, Gemini CLI, Qwen Code, OpenCode, Copilot CLI, Cursor, Devin, Antigravity, and Kiro. To resume a session, simply click on it, and the app will display what Claude Code recorded, including the entire conversation with each tool call on a separate line.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
