On the record

Every problem Valo solves — with receipts.

These are not marketing claims. Each one below is a real, publicly filed issue on Claude Code’s and Codex’s own issue trackers — the same walls hundreds of developers keep hitting. Valo exists because we hit them too.

94 documented issues · 66 still unresolved · across both engines Valo runs (Claude Code and Codex). Every one links to the source — verify it yourself.

Open — still broken todayClosed, never fixedFixed — but it happened

Your work just vanishes

Close the wrong window, hit a context limit, or install an update — and the whole conversation is gone. Resume brings back a fraction, or nothing. It happens on both engines.

What Valo does · Forever History + self-repair

Valo writes every chat to durable storage the moment it happens, and repairs broken sessions on its own. Chats survive restarts, reboots, and reinstalls — forever, and fully searchable.

The receipts · 21 issues, 10 unresolved

Claude Code

Codex

Hit stop, and a blank stranger takes over

This is the one almost nobody names correctly. Interrupt a turn and the CLI is killed before it writes what just happened to disk — so the next thing you type resumes a session that is now empty or broken, and a completely fresh AI spawns in its place with none of your context. It is trained to be helpful, so it reads your recent commits and open files and confidently continues as if nothing happened. You do notice something is off — it "hallucinates," it "stops listening," it does the opposite of what you just asked. You just blame the AI, never knowing a silent reset underneath you was the real cause.

What Valo does · Pause + session auto-heal

Valo treats a stop as sacred. It captures the turns the CLI never flushed to disk, and if the session cannot cleanly resume, it rebuilds your entire conversation into the new one — so you keep talking to the AI that actually has your context, never a blank stranger guessing from your git history. Pause halts cleanly instead of hard-killing to prevent it; silent auto-heal repairs it when it slips through.

The receipts · 22 issues, 16 unresolved

The twist: the reset is invisible, but the damage is loud. So much of what people call "the AI hallucinating," "it ignored me," or "it got dumber" is really this — reported constantly, under the wrong name. The issues below are just the interrupts that error out loudly enough to file a bug.

Claude Code

Codex

It deletes things you never approved

Agents have wiped thousands of untracked files, emptied the trash, and destroyed documents with no explicit instruction — and the reports keep coming.

What Valo does · Safety Guards

Valo’s Safety Guards inspect dangerous actions before they run and stop the ones that cross a line. Four ship built-in, and you can add your own.

The receipts · 6 issues, 5 unresolved

Your secrets leak into the chat

Credentials get printed into tool output, committed to GitHub, and read straight out of .env files — with no redaction.

What Valo does · Password vault + Streamer Mode

Valo keeps secrets in an encrypted vault and injects them at run time, so the AI uses them without ever seeing the values. Streamer Mode scrubs them off your screen too.

The receipts · 11 issues, 9 unresolved

Permission fatigue

Hundreds of identical approval prompts, allow-rules that get ignored anyway, and no clean middle ground between approving once and approving forever.

What Valo does · One-click Allow

Valo’s Allow approves a tool for the whole task in one click — no popups, no death by a thousand prompts.

The receipts · 9 issues, 5 unresolved

It fills up and gets dumber

The longer you talk, the worse it gets — and right at the limit, the tools meant to compact the conversation fail exactly when you need them most.

What Valo does · Context Control

Valo lets you manage what the AI sees: hide the tools, skills, and messages it does not need, edit its instructions live, and hand off cleanly before things pile up.

The receipts · 9 issues, 5 unresolved

It forgets between sessions

Memory that never actually gets applied, instructions dropped after compaction, and auto-memory that corrupts from one session to the next.

What Valo does · Active Memory

Valo’s Active Memory stays dormant and resurfaces only when you touch something it relates to — so it never clogs the context, and hard-won lessons are not repeated.

The receipts · 6 issues, 6 unresolved

Two sessions break each other

Run more than one session at once and they race on the same credentials file — quietly invalidating each other’s login.

What Valo does · Multi-project workspace

Valo is built to run many chats and many projects at once, each held in one window you flip between like browser tabs — without sessions stepping on each other.

The receipts · 4 issues, 4 unresolved

No way to reach it from your phone

Long-standing requests to start, steer, or just check on a session from a phone — still unaddressed.

What Valo does · On the Go

Valo’s On the Go lets you talk to it from your phone over Telegram — text, voice, photos, even approving permissions, from anywhere.

The receipts · 6 issues, 6 unresolved

None of this is a knock on the engines.

Claude and Codex are the best AI models in the world — Valo runs on them. But the app wrapped around them decides whether your work survives, your secrets stay yours, and a stop button is safe to press. That layer is what Valo is.

See everything Valo does →

Home Features Compare Pricing FAQ