Skip to content

Try Lens Agents locally assisted by a coding agent#

Install the full Lens Agents platform on your own machine — in a dedicated local single-node cluster, its own minikube profile isolated from any existing clusters — then launch Prism, Lens Agents' ready-made managed agent, and chat with it in your browser. This is the fastest self-serve path: hand the setup to a coding agent (Claude Code, Codex, OpenCode — CLI or desktop app) and let it drive, installing the Lens Agents admin skill, standing up the platform, and returning both URLs, pausing only for browser sign-ins. To do the setup by hand instead, see Try Lens Agents locally by hand.

The setup prompt#

Open your coding agent and paste this prompt:

Setup prompt

Install the Lens Agents admin skill from https://github.com/lensapp/lens-agents-admin-skill/tree/main/lens-agents-admin and follow it to set up Lens Agents.

The agent installs the skill, stands up the platform, launches Prism, and returns both URLs. It relies on the same host tools as the manual walkthrough — docker, minikube, kubectl, helm (v3.8+), openssl, and curl — and prompts you to install any that are missing, so you can start without them in place. Have two things ready that the agent can't create for you: a Lens ID account (sign up at app.k8slens.dev) and one inference-provider credential for managed inference — an AWS Bedrock API key, or a Microsoft Foundry resource URL and API key with a Claude deployment.

Container-level isolation only

This local setup shares the node's host kernel, so agents run with container-level isolation — the standard sandbox harness, but not microVM isolation. Production deployments add per-sandbox microVM isolation with a Kata Containers or gVisor runtime class, which a local minikube cluster cannot provide. Contact us to scope a production-grade environment.

Run the setup#

To set up Lens Agents with a coding agent:

  1. Open your coding agent and paste the setup prompt.
  2. Install any missing host tools when the agent prompts you.
  3. Complete the browser sign-ins when the agent pauses for them — the Lens ID activation and sign-in described in the manual walkthrough's activation step.

The agent stands up the platform, launches Prism, and returns the platform admin UI URL (http://localhost:3002) and the Prism chat UI URL (http://<slug>.localtest.me:3002).

To install the admin skill manually before running it — or to see the per-agent install commands — see Skills. To do the whole setup by hand, follow the manual walkthrough.

If something goes wrong#

The agent runs the same commands as the manual walkthrough, so the same failures and fixes apply. See Troubleshooting for sandbox startup failures, unreachable chat URLs, and provider mismatches. To tear the trial down, follow Clean up.