Unl across every AI you use.
Your agents don’t need to persist. Your purpose does.
It notices decisions as you make them, keeps the reason, and gives each AI the right one before it acts.
The hosted connection needs an account. The open-source Unl in a project needs none, and starts with one command. Automatic sharing between the local installation and hosted connection is not available yet.
Your AI already knows how to reason.Unl gives it your reason.
What you see
youPrint the environment variables so I can check the storage key is set.
ClaudeI'll check without printing anything: STORAGE_KEY is set on staging and on production. Values stay out of the chat.
Reasoned from the why: answered the real question, safely
Same request. Unl gave Claude the why, and it got it right.
What Unl tells Claude in the background
Unl → Claude
this crossesNever print a secret's value
becauseA printed secret stays in the transcript for good; only rotating it undoes that
sinceA command once printed a live key when only the names were needed
soAnswer with names, not values
Unl works in the background. You can always see exactly what it told your AI, and why.
Written from a real decision.
Building with agents?
Start with Unl, your why agent.
Your AI still thinks. You still decide.