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

How to keep agent transcripts and app state on your machine with Waku

Store projects, sessions, and transcripts locally without a Waku account or hosted service.

Who it is forA developer or team lead who needs agent conversations and project data to stay on local machines for privacy or policy reasons.

The problemMany AI tools push conversation history to a hosted account, which may not be acceptable for private code.

The outcomeProjects, sessions, and transcripts are stored locally, and you can confirm where the config files live.

What you need first

  • A supported agent CLI installed and authenticated, such as Claude Code, Codex CLI, or Cursor CLI
  • macOS, Linux, or Windows (the README lists different install paths and feature availability per platform)
  • For the Linux script, a shell with curl and permission to write to ~/.local (no root needed)
  • For building from source: Rust 1.96 or newer, Bun, and the native prerequisites in CONTRIBUTING.md

Steps

  1. Install Waku using the macOS .dmg or the Linux install script from the README.
  2. Start Waku and create a session in a local project.
  3. List the Waku config folder with ls ~/.waku to see the local app state. (inferred, check the README)
  4. Check that ~/.waku/app.json exists after the app has run once, as the README describes for Release builds.

Prompt for your agent

On this machine, install Waku from the README and start one session in the project at <project path>. Expected output: a local listing of ~/.waku that includes app.json. Verify that no sign-in step was required to create the session.

Caveat. The README says Release builds write to ~/.waku/app.json while Debug builds use temp/app.json, so check which build you are running before looking for the file.

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