DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to continue an earlier agent conversation in a writable room with Peerbridge MCP

Import a Codex or Claude Code history and continue it in a normal room without changing the source.

Credentials. Import reads local session records from other agent tools, so check only the conversations you intend to bring into a room.

Who it is forA developer who had useful work in a past Codex or Claude Code session and wants to resume it inside a governed multi-agent room.

The problemPast agent sessions are scattered across tools and resuming them loses the context and the record of what was decided.

The outcomeA new writable room that carries a bounded source-conversation ID and a SHA-bound context message, while the imported source room stays immutable.

What you need first

  • Python installed for the source demo and source installation
  • A local Git repository for worktree-based work
  • Windows x64 for the portable Alpha 6 ZIP build
  • Agent clients or provider accounts you already use, such as Codex or Claude Code, for live runs

Steps

  1. Open the Agent history import view in the Modern Workbench.
  2. Review the bounded metadata list, which selects nothing by default.
  3. Check only the conversations you want to import.
  4. Select **Continue from history** on the imported conversation to create a writable room.
  5. Confirm the new room shows the SHA-bound context message before you send the next task.

Prompt for your agent

In the PeerBridge MCP control room, import only the Codex conversation <conversation-id> from the agent history list and use Continue from history to create a writable room. Report the new room ID, and verify that the source room remains read-only.

Caveat. Hidden chain-of-thought and uncaptured external terminal history are not imported, and PeerBridge does not label them as visible.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page