TekWeave meets your team where it already works — in your editor, your CI pipeline, and your container runtime.
The TekWeave VS Code extension adds a dedicated sidebar panel for managing environments alongside your code. Launch, snapshot, and restore containers without leaving the editor. Code lens annotations appear inline above test files, showing the environment status and a one-click launch button. Available in the VS Code Marketplace.
ext install tekweave.tekweave-vscode
Stable
Full feature parity with the VS Code extension across IntelliJ IDEA, GoLand, PyCharm, WebStorm, and Rider. The plugin integrates with JetBrains' built-in run configurations — add an TekWeave environment as a "Before launch" step and your container stack starts automatically every time you run your tests. Available in the JetBrains Marketplace.
Settings → Plugins → search "TekWeave"
Stable
TekWeave abstracts over the container runtime so your environment definitions are portable across machines and operating systems. The following runtimes are supported today:
Full support including BuildKit, Docker Compose V2, and multi-platform builds. Recommended for teams on macOS or Windows who prefer a GUI.
Lightweight macOS runtime with no licensing restrictions. TekWeave auto-detects Colima's socket path and configures the Docker CLI context automatically.
Supports both dockerd and containerd backends. TekWeave uses the selected backend transparently — switch between them in Rancher Desktop settings without updating your environment config.
Direct Lima VM integration for teams that prefer a minimal footprint. TekWeave manages the Lima instance lifecycle, starting and stopping VMs as needed.
Rootless container support via Podman's Docker-compatible socket. Ideal for environments where running privileged daemons is restricted by policy.
Connect to a remote Docker host or a dev container over SSH. Useful for teams with shared build machines or air-gapped environments.
The tekweave/setup-action GitHub Action installs the TekWeave CLI, authenticates using a repository secret, and provisions the environment defined in your tekweave.json. The same container stack your developers run locally runs in your CI job — no separate services: blocks to maintain.
# .github/workflows/test.yml
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: tekweave/setup-action@v2
with:
token: ${{ secrets.ORBYT_TOKEN }}
- run: npm testTekWeave publishes an official CLI that integrates with any CI system that can run a shell command. A GitLab CI include template and a CircleCI orb are available from the TekWeave registry, covering auth, environment startup, and teardown in reusable pipeline components.
One environment definition. Works everywhere your code runs.
Read the Integration Docs