Blog
On AI-native development, agentic workflows, and owning your setup.
Claude Code on WhatsApp
A Claude Code skill that puts the agent on WhatsApp. Install in one click from your EnvHaven sidebar. Your subscription powers the model, your workspace holds the bridge, and a plain-markdown memory model means it remembers you across days.
The All New EnvHaven
A skills.sh browser inside the extension, a keyboard command palette, an onboarding card for fresh workspaces, and a sidebar where every feature gets its own focused panel.
Why Your AI Agent Keeps Asking Permission
Every major AI coding tool asks permission before acting. Those prompts protect your laptop. In a container with nothing personal on it, they're just in the way.
Custom Domains: Add a CNAME, We Handle the Rest
Point your own domain at an EnvHaven workspace with a single DNS record. SSL is automatic. No special account required.
Three Tiers, Docker, and What Changed
Existing subscriptions are now Hobby. Plus and Pro add more resources and Docker access inside workspaces. Here's what changed and why.
Your Tools, Your Keys, Your Models
Twelve AI coding tools built-in. Authenticate with your own API keys and talk directly to the providers. Nothing is proprietary.
Who Owns Your Dev Environment?
Cloud dev environments are convenient until the vendor changes their mind. Owning your environment means your workflow survives regardless.
What Happens When Claude Code Gets Full Access
The --dangerously-skip-permissions flag isn't actually dangerous if you're not running it on your laptop. A week of unrestricted Claude Code in a container.
The Local Editor Problem
You shouldn't have to choose between your local editor and remote AI agents. Haven CLI bridges the two with bidirectional file sync.
Standard Docker. Standard Linux.
No proprietary config format. No vendor YAML. A real Linux machine with Docker, SSH, and your tools. That's the whole thing.