Manage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared).
Scanned 5/27/2026
Install via CLI
openskills install kurtosis-tech/kurtosis---
name: context-manage
description: Manage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared).
compatibility: Requires kurtosis CLI.
metadata:
author: ethpandaops
version: "1.0"
---
# Context Manage
Manage Kurtosis contexts for connecting to different Kurtosis instances.
## What are contexts?
Contexts define which Kurtosis instance the CLI talks to. The default context is `default` which connects to the local engine (Docker or Kubernetes).
## List contexts
```bash
kurtosis context ls
```
Shows all configured contexts and which one is active.
## Add a context
```bash
kurtosis context add <context-name>
```
## Switch context
```bash
kurtosis context set <context-name>
```
After switching, restart the engine or portal as needed.
## Remove a context
```bash
kurtosis context rm <context-name>
```
## Common workflow
```bash
# Check which context is active
kurtosis context ls
# Switch to a different environment
kurtosis context set staging
# Verify the switch succeeded
kurtosis context ls
# Start portal if using a remote context
kurtosis portal start
# Switch back to local
kurtosis context set default
```
## Error handling
| Scenario | Behavior | Resolution |
|----------|----------|------------|
| Switch to non-existent context | Command fails with error | Run `kurtosis context ls` to see available contexts |
| Remove active context | Command fails — cannot remove active | Switch to another context first with `kurtosis context set` |
| Engine running after switch | Engine still connected to old context | Run `kurtosis engine restart` after switching contexts |
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.