Our take
Newless than six months old and changing fast- Activity
- 86
- Community
- 28
- Issues
- 84
- Pull requests
- 67
- Releases more often than 87% of the projects we track
Wake addresses the practical problem of fragmented local agent histories with a broad, privacy-conscious desktop workflow, but it is a very new project whose development is heavily concentrated in one contributor.
Good fit if
- You use multiple supported coding agents and want to search and resume their local sessions in one place.
- You want agent history and MCP access to stay on your machine, with remote access limited to hosts you configure.
- You are comfortable using a fast-changing MIT-licensed project and, on Linux or Windows, experimental platform support.
Look elsewhere if
- You need support for Windsurf or Trae, which the project says are unsupported, or for cloud-only agents such as Amp, Factory, and Warp.
- Your workflow requires a stable, mature desktop tool with development responsibility spread across several contributors.
- You need Windows remote-host support, which Wake does not provide.
All health signals
| Last commit | 2026-10-16 (1 day ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 51 (latest v0.9.5, 2026-10-16) |
| Contributors | 9 (top contributor: 92% of commits) |
| Issues closed, last 90 days | 41 (typically closed in 1 day) |
| Pull requests merged, last 90 days | 14 (typically merged in 0 days) |
| Project age | 2 months |
Checked on 2026-10-18 with the GitHub API.
Overview
Wake is a native desktop app built with Rust and GPUI that brings coding-agent sessions from local files and databases into one searchable workspace. Instead of hunting through agent-specific folders, developers can browse conversations, read transcripts, and resume work in the right project and terminal. The app is macOS-first; Linux and Windows support is experimental.
Wake reads agent data locally and read-only, and its optional plugins, MCP server, and CLI let agents search prior sessions and use them as project context. It is aimed at developers who use several coding agents and want a shared view of their history without moving that data to a hosted service.
Key Features
- Indexes session histories from a wide range of coding agents, grouping sessions by agent and project.
- Searches titles and full transcripts, including code and CJK text, and jumps to matching passages.
- Displays transcripts with tool calls, images, thinking, and syntax highlighting.
- Resumes sessions in supported terminals or Claude and Codex Desktop, in the relevant project folder.
- Connects Claude Code and Codex through plugins, and exposes read-only search and transcript tools through MCP and a CLI.
- Tracks agent memory and instruction files, with project activity insights such as heatmaps and weekly trends.
- Can mirror session data from remote machines over SSH and rsync, without writing to the remote host.
Use Cases
- A developer switching among Claude Code, Codex, Cursor, and other supported agents can search past conversations from one desktop app.
- Someone returning to a codebase can find earlier decisions or debugging discussions and provide that context to a new agent session.
- Teams or individuals with large local agent histories can identify space-consuming sessions and export, organize, or remove them.
- Developers working across machines can browse and search mirrored sessions from configured remote hosts.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
On macOS, download the latest app from the Wake releases, unzip it, and move Wake to Applications. To build from source:
git clone https://github.com/iAmCorey/Wake && cd Wake
scripts/make-app.sh
See the README for Linux and Windows installation, plugins, MCP, CLI, and build details.
Alternatives
- opcode: Opcode focuses on Claude Code projects and sessions, with custom agents and usage review; Wake searches sessions from coding agents more broadly.
- atlas: Atlas runs multiple coding agents on a codebase and links their sessions to Git commits, while Wake focuses on finding and resuming past conversations.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| Wake | Rust | MIT | 1.5k | New |
| opcode | TypeScript | AGPL-3.0 | 22.4k | Maintained |
| atlas | Rust | Apache-2.0 | 8.9k | New |
Considerations
- The repository is less than six months old and is changing quickly. It has frequent releases and recent commits, but most of the code comes from one person, creating contributor-concentration risk.
- macOS is the primary platform. Linux and Windows are explicitly experimental, and Windows remote hosts are unsupported.
- Wake relies on a Rust toolchain to build from source. The README describes CI and test commands, but the supplied requirements data does not report a test suite.
- The app reads many agent storage formats, which can change as those agents evolve. Some agents are not supported, including tools whose data is encrypted or cloud-only.
- Remote synchronization requires prompt-free SSH and rsync on both ends. Wake assumes default paths on remote hosts, and only session data is copied.
- Wake is MIT-licensed. Its privacy approach is local and read-only for agent data, but users should still review which local folders they add and which remote hosts they configure.
Found this useful?
Share it with someone who would like Wake.