envhaven
Health Gecti
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Community trust — 22 GitHub stars
Code Uyari
- network request — Outbound network request in cli/scripts/bundle-mutagen.ts
- crypto private key — Private key handling in cli/src/commands/connect.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
This tool provides a containerized, remote development environment specifically designed for AI coding agents. It allows developers to run autonomous AI tools in an isolated workspace, keeping the local machine safe from unintended changes or credential leaks.
Security Assessment
The tool is designed to execute shell commands and manage isolated environments, which is expected for its purpose. The audit flagged an outbound network request in a bundling script, which is typical for setup operations. It also handles private keys within its connection module, a standard requirement for establishing secure remote sync sessions. No hardcoded secrets or dangerous permission requests were found. Overall risk: Medium. The tool is built to give AI agents "full system access" within a container, which is safe by design, but the handling of private keys means users should ensure their deployment environment is secure.
Quality Assessment
The project is actively maintained, with its most recent code push occurring today. It is fully licensed under the standard MIT open-source model. While the repository has a modest community following at 22 GitHub stars, this is normal for an actively developed niche tool in the emerging AI agent workflow space.
Verdict
Safe to use, provided you review the remote connection configurations and trust the isolated server environment you deploy it to.
Batteries-included development environment for agentic workflows.
EnvHaven
Batteries-included development environment for agentic workflows.
As tools like Claude Code, OpenCode and Codex gain agency, they need full system access to be effective. Running them locally carries risk (rm -rf accidents, credential leaks) and friction (installing complex runtimes).
EnvHaven solves this. It's a remote environment that spins up in seconds, with sane defaults and every major AI coding tool and built-in, fully isolated from your personal machine and pre-configured to bypass permissions out of the box.
Workflow Freedom:
- Browser-only — Deploy the image, open VS Code in your browser, run
opencode. Zero setup. - Local editor + remote AI — Use the Haven CLI to sync your project. Edit in Neovim, Zed, Jetbrains, et al. while agents run in the container. Changes sync in ~200ms.
Why EnvHaven
🛡️ Zero-Risk AI environment
Give autonomous agents full access in a containerized environment. If they break something, nuke the workspace and start over. Your local machine stays untouched.
🖥️ Pick Up Where You Left Off
Start Claude Code on your laptop, close the lid, resume from your desktop—same session, same state. Your AI agents and dev servers keep running while you're away. Come back from any device.
🌲 Evergreen AI Tooling
The landscape moves too fast to manage manually. EnvHaven ships with 12+ AI CLI tools (Claude Code, OpenCode, Aider, Codex, Gemini CLI, Goose, Mistral Vibe, etc.) built-in and ready to run.
🌐 Instant Public URLs (Managed only)
Every managed workspace gets a wildcard *.envhaven.app domain. Deploy a web app, webhook receiver, or Discord bot—live instantly. No ngrok, no tunnels, no DNS.
💾 Persistent & Owned
Unlike ephemeral environments (Codespaces) or walled gardens (Replit), EnvHaven workspaces are persistent Linux environments you own.
⚡ Open Model
- Self-Hosted: Free forever, open-source Docker image and CLI. Run it on your own server.
- Managed ($10/mo): Zero-config hosting with custom domains, always-on workspaces, and no DevOps.
Who It's For
| Persona | Use Case |
|---|---|
| Vibe Coders | That ship by prompting their way to products. Need a "magic box" where code just runs, already fully setup. |
| AI-Native Devs | Power users of agentic coding tools like Claude Code or OpenCode that want a standardized, pre-configured backend for their agents. |
| Setup Purists | Developers married to their beautifully tuned and customized editor. Use Haven CLI to keep your workflow while agents run wild in a contained environment. |
| Bot Builders | Those who vibe-code 24/7 persistent scripts (Discord, Telegram or even trading bots). |
Quick Start
Path A: Browser-Only (Zero Setup)
Deploy the image and code immediately in the browser.
docker run -d \
--name envhaven \
-p 8443:8443 \
-p 2222:22 \
-e PASSWORD=password \
-e SUDO_PASSWORD=password \
ghcr.io/envhaven/envhaven:latest
- Open
https://localhost:8443(Password:password) - Open terminal—you're dropped into a persistent session
- Run
opencode,claude, oraiderand start coding
Multiple AI tools at once? Click + in the footer or use the sidebar to create new terminals. Each runs in its own persistent session—close your browser and they keep running.
Path B: Local Editor + Remote AI (Haven CLI)
Use your local editor. Files sync bidirectionally. Agents run in the container.
1. Install Haven CLI
curl -fsSL https://envhaven.com/install.sh | sh
2. Connect to your workspace
cd my-project
# Managed workspace (shorthand)
haven connect . myproject-alice
# Self-hosted container
haven connect . [email protected]:2222
Files sync in ~200ms.
3. Run remote commands
haven opencode # Runs OpenCode in the container
haven make build # Runs make in the container
haven npm install # Runs npm in the container
Self-hosted? You'll need to configure SSH keys first. See SSH Access.
What's Included
The image (ghcr.io/envhaven/envhaven) comes batteries-included.
AI Coding Agents
No API keys are pre-set. You can set them directly in the UI via the bundled EnvHaven Extension in code-server.
You can also provide your own keys via env vars (-e ANTHROPIC_API_KEY=...) or config files.
| Tool | Command | Description |
|---|---|---|
| OpenCode | opencode |
SST's autonomous coding agent |
| Claude Code | claude |
Anthropic's official CLI |
| Aider | aider |
AI pair programming |
| Codex | codex |
OpenAI's coding agent |
| Gemini CLI | gemini |
Google's AI in terminal |
| Goose | goose |
Block's developer agent |
| Mistral Vibe | vibe |
Powered by Devstral |
| Qwen Code | qwen |
Alibaba's coding assistant |
| Amp | amp |
Sourcegraph's coding agent |
| Augment | auggie |
Context-aware coding agent |
| Kiro | kiro-cli |
AWS-powered AI CLI |
| Factory Droid | droid |
Factory's AI agent |
Zero-Friction Permissions
EnvHaven workspaces are structurally isolated. The default permission prompts from the AI tools add friction without the added value: The container IS the sandbox, so all agents are pre-configured for maximum permissiveness out of the box. No approval prompts, no confirmation dialogs. Agents execute immediately.
You can re-enable prompts per tool by editing the relevant config or unsetting the env var. See the in-workspace AGENTS.md for details.
Runtimes & SDKs
| Language | Version | Notes |
|---|---|---|
| Node.js | 20.x | LTS |
| Bun | Latest | Fast JS runtime |
| Python | 3.12 | Managed via uv |
| Go | 1.22 | |
| Rust | Stable | Via rustup |
Dev Tools
- Core:
zsh,git,curl,wget,zip,unzip - Utils:
ripgrep,fd,jq,sqlite3,htop - Media:
ffmpeg(video/audio),playwright(browser automation) - Integrations:
gh(GitHub CLI),docker(client)
Haven CLI Architecture
The CLI enables a hybrid workflow: Local Editor + Remote Compute.
- Latency: ~200ms bidirectional sync.
- Compatibility: Works with any editor.
- Independence: The sync daemon runs in the background; close the CLI and sync continues.
┌────────────────────────────────────────────────────────────────────────┐
│ YOUR MACHINE │
│ │
│ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
│ │ Local Editor │ │ Haven CLI │ │ Sync Daemon │ │
│ │ │ │ │ │ │ │
│ │ nvim/lazyvim │ │ haven connect │ │ │ │
│ │ emacs/doom │ │ haven status │ │ Continuous │ │
│ │ helix │ │ haven <cmd> │ │ bidirectional │ │
│ │ │ │ │ │ ~200ms latency │ │
│ └────────┬────────┘ └────────┬────────┘ └────────┬────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────────────────────────────────────────────────────────┐ │
│ │ ~/projects/myapp/ │ │
│ └──────────────────────────────────────────────────────────────────┘ │
│ ▲ │
│ │ │
│ ▼ │
│ ┌──────────────────────────────────────────────────────────────────┐ │
│ │ /config/workspace/myapp/ │ │
│ └──────────────────────────────────────────────────────────────────┘ │
│ ▲ ▲ ▲ │
│ │ │ │ │
│ ┌────────┴────────┐ ┌────────┴────────┐ ┌────────┴────────┐ │
│ │ Claude Code │ │ OpenCode │ │ aider │ │
│ │ Long-running │ │ Long-running │ │ Task-based │ │
│ │ AI sessions │ │ AI sessions │ │ AI sessions │ │
│ └─────────────────┘ └─────────────────┘ └─────────────────┘ │
│ │
│ ENVHAVEN CONTAINER │
└────────────────────────────────────────────────────────────────────────┘
Why this matters:
- AI agents need contained compute: They require massive context windows, long-running processes, specific toolchains, and might do dangerous stuff some time.
- You need your editor: You rely on your custom keybindings, themes, and muscle memory.
- Flexibility: Both workflows work independently or together.
Docker Compose
For persistent deployments, use docker-compose.yml with .env:
cp .env.example .env # Copy and edit with your passwords/API keys
docker compose up -d
Or use inline environment variables for quick testing:
services:
envhaven:
image: ghcr.io/envhaven/envhaven:latest
container_name: envhaven
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- PASSWORD=password # Web UI password
- SUDO_PASSWORD=password # sudo/SSH password
volumes:
- ./config:/config # Persist home directory
ports:
- 8443:8443 # Web UI
- 2222:22 # SSH Access
restart: unless-stopped
See Configuration Reference for all options including AI API keys and SSH setup.
SSH Access
SSH enables the Haven CLI and direct terminal access.
| Setup | SSH Host | Haven CLI |
|---|---|---|
| Managed | ssh-{subdomain}.envhaven.app |
haven connect . myproject-alice |
| Self-hosted | your-server:2222 |
haven connect . abc@your-server:2222 |
Self-hosted setup: Import your GitHub keys automatically:
environment:
- PUBLIC_KEY_URL=https://github.com/yourusername.keys
ports:
- "2222:22"
See Configuration Reference for all SSH options.
Documentation
- AI Tools Guide — Setup guides, API keys, and usage examples for all 12+ AI coding tools
- Configuration Reference — Complete env vars, SSH setup, Docker mods, and compose examples
- Development Guide — Building from source, testing, and contributing
- Haven CLI — CLI source and architecture
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi