JianHe Is a Floating Prompt Box for Everyone Juggling Five AI Tools

Yesterday someone shipped a small tool called JianHe (笺盒), and the idea behind it is more useful than it first sounds. It doesn’t try to be smarter than your AI tools. It tries to make sure you never lose the things you taught them.

The builder runs Claude Code, Codex, Antigravity and WorkBuddy side by side. They also run CC CLI and PI inside a Linux VM. That is a lot of surfaces, and each one has its own habits, its own place to store instructions, and its own way of forgetting what you told it last week. Most of their day went to getting these separate AI systems to share knowledge, which meant copying prompts into one window, tweaking them, and moving skills around by hand. Then they left the work laptop at the office, and every skill they wrote that day was stuck there until morning. If you have ever written a really good prompt on one machine and needed it on another, you know exactly how that feels.

The twist is that JianHe doesn’t try to be another big AI app. There is no new chat window to learn and no new model to pay for. It floats on your screen and stays nearly invisible until you need it. The name comes from the Chinese word jian, meaning small slips of paper, which here stand for your prompts and skills. Think of a stack of sticky notes that follows you from tool to tool. The box keeps those slips in one place. It uses a local-first workflow, so your assets live with you instead of inside any single tool. That matters because the tools will change. Next quarter you may drop one and add another, and your best prompts should survive that swap without a rewrite.

Here is a mini-workflow you can borrow, whether you use JianHe or not:

  1. Gather every prompt and skill you reuse, from each AI tool and each machine, into one place. Do a quick sweep of your chat histories, your config folders and your notes app. Most people find they have three or four versions of the same prompt scattered around, so pick the best one and retire the rest.
  2. Give each one a short, searchable name so you can find it mid-task. Name it by the job, like “bug-report-triage” or “meeting-to-actions”, not by the tool. If you can’t guess the name in two seconds, you won’t use it.
  3. Keep the collection on the machine you work on, and open it from a floating panel instead of switching windows. Every window switch breaks your focus, and a panel that sits on top of whatever you are doing cuts that cost to almost nothing.
  4. Copy from that one source into whichever model you are using, so you stop rewriting the same prompt per platform. When you improve a prompt, improve it in the collection first, then paste the new version out. That way the collection stays the source of truth and the tools stay downstream.

Pro tip: the next time you write a good prompt, save it right away. If it only exists in a chat tab, you will lose it. A useful habit is to save it the moment it gives you a result you liked, while you still remember why it worked. Add one line of context under the name, such as what input it expects and what output you got. Future you will thank you. That is the same gap that left this builder stuck at home without their work.

Pro tip: if you split your work between a laptop and a VM like they do, check how your prompt library moves between machines before you commit to it. Ask yourself three things. Can I get my collection onto a second machine in under a minute? Can I read it without the app if the app breaks? Does it work when I am offline? A plain, local format that you can back up yourself beats a clever format you can’t export. Local-first only helps if you also have a simple way to carry your files across.

One more small practice worth stealing: do a ten-minute review every Friday. Delete prompts you never touched, merge near duplicates, and promote the two or three you used most to the top. A small, trusted collection beats a huge one you never open.

The post is light on feature details, so the demo video and the site are where you will see what it does. It is a solo builder’s project, and they are asking for feedback. If you juggle several AI tools every day, take a look and tell them what is missing, especially if you work across more than one machine, because that is the exact pain this tool grew out of 🧰

Site: https://jianhe.neodaas.com/

I built a prompt management tool to solve my own pain points — and it might be exactly what you’re looking for.
by u/Historical-Skirt2883 in PromptEngineering

Scroll to Top