
Research
Node.js Fixes AsyncLocalStorage Crash Bug That Could Take Down Production Servers
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.
@vibe-kit/dagger
Advanced tools
Local sandbox provider for Vibekit using Dagger.
The @vibe-kit/dagger package enables Vibekit to run AI coding agents in isolated, containerized environments on your local machine. This provides an alternative to cloud-based sandboxes, offering faster iteration, offline development, and cost savings.
The local provider is automatically available when you install Vibekit. System dependencies are installed automatically when you first use the local provider:
# Initialize with local provider
vibekit init --provider dagger
# Or add to existing project
vibekit dagger setup
If automatic installation fails, you can install dependencies manually:
# Install Docker (platform-specific)
# See: https://docs.docker.com/get-docker/
# Install Dagger
curl -fsSL https://dagger.io/install.sh | bash
# Verify installation
dagger version
import { createLocalProvider } from '@vibe-kit/dagger';
// Create a local provider
const provider = createLocalProvider();
// Create a sandbox instance
const sandbox = await provider.create(
{ NODE_ENV: 'development' }, // environment variables
'claude', // agent type
'/vibe0' // working directory
);
// Execute commands
const result = await sandbox.commands.run('npm install');
console.log(result.stdout);
// Clean up
await sandbox.kill();
import { createLocalProvider, LocalDaggerConfig } from '@vibe-kit/dagger';
const config: LocalDaggerConfig = {
// Configuration options for the local provider
};
const provider = createLocalProvider(config);
The local provider consists of several key components:
The local provider supports all Vibekit agent types:
assets/dockerfiles/Dockerfile.claudeassets/dockerfiles/Dockerfile.codexassets/dockerfiles/Dockerfile.opencodeassets/dockerfiles/Dockerfile.geminiEach agent type can have its own optimized container image for better performance.
Local sandboxes run in Docker containers with the following isolation:
This package implements the same SandboxProvider interface as other Vibekit providers:
interface SandboxProvider {
create(envs?, agentType?, workingDirectory?): Promise<SandboxInstance>;
resume(sandboxId: string): Promise<SandboxInstance>;
}
interface SandboxInstance {
sandboxId: string;
commands: SandboxCommands;
kill(): Promise<void>;
pause(): Promise<void>;
getHost(port: number): Promise<string>;
}
This ensures you can swap between local and cloud providers seamlessly.
Docker not running:
# Check Docker status
docker ps
# Start Docker Desktop (macOS/Windows)
# Or start Docker daemon (Linux)
Dagger not found:
# Reinstall Dagger
curl -fsSL https://dagger.io/install.sh | bash
# Check PATH
which dagger
Permission errors:
# Add user to docker group (Linux)
sudo usermod -aG docker $USER
# Then log out and back in
Enable verbose logging for troubleshooting:
export VIBEKIT_LOG_LEVEL=debug
# Your Vibekit commands here
See the main Vibekit contribution guide for general guidelines.
# Clone the repository
git clone https://github.com/vibekit/vibekit.git
cd vibekit
# Install dependencies
npm install
# Build the dagger package
cd packages/dagger
npm run build
# Run tests
npm test
MIT - see LICENSE for details.
FAQs
Local sandbox provider for Vibekit using Dagger
The npm package @vibe-kit/dagger receives a total of 2 weekly downloads. As such, @vibe-kit/dagger popularity was classified as not popular.
We found that @vibe-kit/dagger demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.

Research
/Security News
A malicious Chrome extension steals newly created MEXC API keys, exfiltrates them to Telegram, and enables full account takeover with trading and withdrawal rights.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.