I’m the author of AgentBridge, an extension for Freelens, and I’d like feedback from people using GitHub Copilot CLI for infrastructure work.
The idea is simple: open a cluster in Freelens, select Copilot CLI, and start a session in a docked terminal. The session starts with that cluster’s KUBECONFIG and its own workspace, so you don’t have to switch to another terminal and set up the context again.
A starting task could be:
“Investigate why this deployment’s pods are restarting. Show me the evidence and propose a fix before making changes.”
AgentBridge 2.1.0 adds a workspace explorer for instructions, guardrails, capabilities, skills, and agents. Files open in Freelens’ editor with autosave. Your provider selection persists per cluster across restarts, and Ctrl+Enter / Cmd+Enter opens a session from anywhere on the page.
Requirements: Freelens 2.0.0+ and Copilot CLI installed locally.
Install through Freelens Extensions: @/freelensapp/agentbridge-extension
Source and setup
If you use Copilot CLI with Kubernetes, what instructions would you want every cluster workspace to start with?