Hvelv Free
€0forever
- Local storage scan
- Agent runway estimate
- Safety evidence
- Manual reproducible-cache cleanup
- No scheduled or cloud actions
Your context stays.
The weight moves.
Hvelv finds developer storage that can move safely, explains what to do next, encrypts cold agent sessions with your key, and restores the one session you choose.
- Your key stays in Keychain
- Your cloud account
- One named session at a time
Not tied to one agent. Codex, Claude, and OpenCode are the first local adapters. The same evidence model is designed to extend across Grok, Kilo Code, Hermes, OpenClaw, and other coding tools.
NO DATA SENT01Critical boundary detected9.9 GB free on Macintosh HD
Recover the safe cache first.0.5 GB is reproducible. Agent context stays locked.
Adapter-ready
- Codex
- Claude
- OpenCode
- Grok
- Kilo Code
- Hermes
- OpenClaw
- and more
Every byte gets a verdict.
Hvelv joins filesystem, process, Git, and agent-session evidence before it presents an action.
| Storage | Evidence | Decision |
|---|---|---|
| Package and build caches | Inactive · reproducible | Safe to clean |
| Coding-tool worktrees | Git + adapter evidence | Review required |
| Named agent sessions | age encrypted · verified | Selective restore |
| OpenCode live database | Process currently active | Locked |
Four checks. No guessing.
The workflow stays understandable even when your storage does not.
- 1
Check the runway
Estimate whether the Mac has enough memory, CPU, disk reserve, thermal headroom, and Docker capacity for the agents and build you intend to run.
- 2
Find the weight
Scan known developer locations and selected repositories. Active processes lock themselves automatically, regardless of which supported coding tool created the files.
- 3
Protect the context
Review evidence, then stream cold sessions through zstd and local age encryption to your own vault.
- 4
Restore by name
Open the encrypted catalog, select one session, verify every hash, and continue in its original harness.
A real desktop tool, not another cloud dashboard.
Hvelv works where the files live. Cloud storage holds encrypted cold context; active databases and current sessions remain on your Mac. Before an agent starts, the local runway estimates safe concurrency for subagents, builds, and Docker, then returns actionable remediation through the same MCP evidence model.
See system requirements
Useful for free. Worth paying for.
The free app handles today’s storage pressure. Hvelv+ keeps the pressure from returning.
Hvelv+
€5+one time · you choose
- Everything in Free
- Maintenance schedules
- Encrypted cloud archive and selective restore
- Worktree cleanup and removal review
- MCP control surface
- Lifetime updates
What Hvelv protects.
Clear answers about cleanup, cloud archives, worktrees, encryption, resource readiness, and coding-tool compatibility.
What storage can Hvelv safely clean?
Hvelv identifies inactive, reproducible developer caches and presents the exact path, size, process evidence, and recovery behavior before cleanup. Sessions, active databases, and unfinished work stay locked unless you explicitly archive or review them.
Does Hvelv work with Codex, Claude Code, OpenCode, and other coding tools?
Codex, Claude, and OpenCode are the first local adapters. Hvelv uses standard Git and MCP boundaries so Grok, Kilo Code, Hermes, OpenClaw, and other tools can be added without weakening the same safety evidence.
Can Hvelv archive one coding-agent session to cloud storage?
Yes. Hvelv streams a selected cold session through compression and local age encryption, uploads it to your Backblaze B2, Cloudflare R2, or rclone-compatible vault, and keeps an encrypted catalog so you can restore that named session later.
Can Hvelv remove old Git worktrees?
Only after a desktop review proves the worktree is clean, unlocked, pushed, tracked upstream, and no longer tied to an active agent session. Dirty, unpushed, locked, or ambiguous worktrees remain protected.
Where are encryption keys and cloud credentials stored?
The private encryption identity and provider credentials stay in macOS Keychain. Cloud storage receives encrypted objects and an encrypted catalog, not readable prompts, project paths, branch names, or session contents.
Can coding agents control Hvelv through MCP?
Hvelv includes an optional local stdio MCP server for inspection, scheduling, worktree evidence, encryption-key setup, and cleanup previews. Destructive or paid actions retain their desktop approval and license boundaries.
Can Hvelv tell an agent whether this Mac can handle more subagents or Docker?
Yes. The local readiness check combines current memory, swap, CPU load, thermal state, protected disk reserve, build overhead, Docker state, and declared per-agent requirements. It returns a conservative safe, constrained, or unsafe assessment with a suggested concurrency ceiling and remediation codes; it never promises exact performance.
Make room without losing the thread.
Hvelv is being verified locally on its first Mac before downloads open. Upgrade only when scheduling, cloud restore, worktree actions, or MCP control earns its place.