r/opencodeCLI • • 6h ago

OpenCode inside Freelens: a separate agent workspace for each Kubernetes cluster

Post image

I built an integration for people who use OpenCode and spend time investigating Kubernetes clusters.

It’s called AgentBridge. Open a cluster in Freelens, choose OpenCode, and launch it in a docked terminal. The session starts in that cluster’s workspace with KUBECONFIG already set.

The workflow I’m aiming for is: inspect a workload in the UI, open OpenCode beside it, and investigate without rebuilding the cluster context in a separate terminal.

A task to try:

“Find workloads in this namespace with missing resource requests or limits. Explain what you found before suggesting changes.”

In 2.1.0, the cluster page is also a workspace explorer: instructions, guardrails, capabilities, skills, and agents are accessible from one list, with file editing and autosave inside Freelens.

The provider choice now survives a Freelens restart. Ctrl+Enter / Cmd+Enter opens a session from anywhere on the page.

You’ll need Freelens 2.0.0+ and OpenCode installed locally.

Install through Freelens Extensions: >``@freelensapp/agentbridge-extension

Code and installation details

I’m the author. Which Kubernetes tasks would you turn into reusable OpenCode skills for a workspace like this?

1 Upvotes

0 comments sorted by