✓It Still Works
  • Home
  • Search
  • Discover
  • Catalogue
  • Categories
  • What changed
  • Developer repos
  • How we check
  • Developer utilities
  • Games and play
  • Everyday tools
  • Music and audio
  • Images and photos
  • Save and convert media
  • Writing and publishing
  • Draw and diagram
  • Coding and upskilling
  • Cloudflare (4)
  • Vercel (3)
  • GitHub Pages (2)
  • Google Cloud (2)
  • nginx (self-hosted) (2)
  • Google (1)
  • Netlify (1)
712 checks loggedEvery listing, every sweepSign in
Theme
✓It Still Works
Sign in

Every listing is checked on a schedule. No numbers we cannot measure.

How we checkGraveyardSubmit something
  • Discover
  • Catalogue
  • Changes
  • Repos

I understood

share memory across tools

Not what you meant?

  • see token spend across Claude Code and Cursor
  • search coding memory
  • share session HTML
  • keep session memory across coding-agent chats

Tools(5)

share memory across tools · keep project decisions in a local agent memory · see token usage across several coding tools in one place · grab a tiny single-purpose tool instead of writing one

5 listings shown. Every result was live at its last check.

  1. Stop re-explaining your codebase every session.

    Why this one

    • share memory across tools
    • persist coding context

    On the record

    • Free
    • No signup
    • Your own API key
    • First check

    Last checked 3 days ago

    Open↗
  2. Local-first memory shared across coding agents

    Why this one

    • keep project decisions in a local agent memory
    • continue a task in a different coding agent

    On the record

    • Free
    • No signup
    • First check

    Last checked 3 days ago

    Open↗
  3. One place to manage providers, routing, MCP and skills across every coding CLI

    Why this one

    • see token usage across several coding tools in one place
    • switch a coding CLI between providers without editing config by hand

    On the record

    • Free
    • No signup
    • First check

    Last checked 3 days ago

    Open↗
  4. Small tools, each published with the AI transcript that built it

    Why this one

    • grab a tiny single-purpose tool instead of writing one
    • read the prompt and transcript behind a tool before trusting it
    • see what prompt-driven development produces in practice

    On the record

    • Your own API key
    • No signup
    • 4 checks

    Last checked 4 days ago

    Open↗
  5. Open-source memory for your AI assistants

    Why this one

    • recall across tools
    • save assistant knowledge

    On the record

    • Free
    • No signup
    • First check

    Last checked 3 days ago

    Open↗