v1.6.0-rc.1

Released: July 22, 2026

The first release candidate on the 1.6 track, opening a new cycle after the 1.5 stable line. The headline is control: a new Tool Access editor that lets you allow- or deny-list exactly which MCP tools an Agent Gateway proxy exposes, and Connect tabs that turn "how do I point my client at this proxy?" into a single paste. Alongside it, Canvas gives AI-authored dashboards an editable, shareable gallery, a new NATS monitoring extension lands, and every credentialed source can now run multiple accounts side by side in their own tabs. Install from the kunobi-unstable channel to try it; the stable track is unchanged.

What's New

Canvas

• Let AI answer with a dashboard, not just text — a connected assistant (or Kunobi's own Cloud AI) can lay any answer out as a canvas: a live, multi-card view it composes to show you exactly what it means, instead of only describing it. It has a rich palette to express itself — rich text and highlighted callouts, tables and key/value pairs, stats with sparklines, charts, relationship graphs, heatmaps, progress bars and gauges, timelines, step-by-step runbooks, collapsible trees, JSON/YAML, syntax-highlighted code, side-by-side diffs, log views, Git commit views, and buttons that deep-link straight into Kunobi.
• The canvas is yours to keep and shape — every canvas an agent creates lands in a searchable gallery. Open one and rearrange, resize, rename or annotate its cards to fit how you read them; export and import canvases as portable files to save or share; and Kunobi keeps them in sync across every open window.

Agent Gateway

• Control which MCP tools a proxy exposes — from the UI — every Agent Gateway MCP proxy gains a Tool Access tab. Block dangerous tools with a deny-list, restrict to a safe set with an allow-list, or mix the two — all without writing a rule by hand. Enforcement hides denied tools from a client's tool listing and refuses their calls (prompts and resources are untouched). It's fail-safe by construction: an empty policy exposes everything exactly as before, "expose nothing" can never silently invert to expose-all, and a broken policy fails closed rather than open. Open it fast with the Tool Access chip in the action bar or the r shortcut.
• Point any client at a proxy in one paste — proxies get a Connect tab. For MCP proxies it leads with a one-command setup for the clients that support it (claude mcp add, codex mcp add, code --add-mcp) and shows the real config shape and file path for Claude Code, Claude Desktop, Cursor, VS Code and Codex — each in its own genuine format, with a link to the vendor's MCP docs. The LLM proxy's Connect tab gets the same treatment. No more copying a raw list of target IDs and guessing the endpoint.

Extensions

• NATS monitoring extension — a new extension surfaces a NATS deployment's full topology as eight drillable kinds — Server, Connections, Accounts, Streams, Consumers, Routes, LeafNodes and Gateways — with relations, a topology graph and detail panels, sourced entirely from NATS's read-only monitoring endpoint. A Latest messages tab on any JetStream stream browses recent messages (sequence, subject, time, size and preview) with a single-message detail view in UTF‑8, hex or base64. It's live-verified against a 2.1‑billion‑message production cluster. This is a Pro-plan feature.
• Run multiple accounts of the same source, each in its own tab — credentialed sources move from one active connection app-wide to per-tab multi-source, matching how Kubernetes clusters already work. NATS, GitHub, GitLab, Bitbucket, Ceph and Cloudflare can each be connected several times at once — one org or cluster per tab — and every tab tracks its own connection status and live data independently.
• More reliable installs and updates — installing or updating an extension is now transaction-safe: your per-extension configuration is preserved across updates, the old process is fully shut down before it's swapped, and extension state survives a failed or interrupted update instead of being wiped. Extension binaries also carry a stable code-signing identifier now, so macOS stops re-prompting for keychain access every time an extension's dependencies change.

Elsewhere

• Copy from the log viewer — select a single line or a contiguous block in the log viewer (Shift+↑/↓, or click then Shift+↕) and copy it with Ctrl/Cmd+C as clean, layout-matching plain text (timestamp · source · level · message, ANSI stripped). This also fixes a macOS bug where Cmd+C did nothing in the log viewer because the native Edit ▸ Copy shortcut swallowed the keypress.
• Detail sidebar for source entities — credentialed sources gain an entity detail right-sidebar, matching the Kubernetes drilldown, so you can inspect a selected row's full detail without leaving the table.
• In-app About page from the macOS App menu — Kunobi ▸ About now opens an in-app About page instead of the system dialog.

Improvements

• GitOps views run on real cluster resources — under the hood, the Flux and ArgoCD trees now read your cluster's real Kustomization, HelmRelease, Application and ApplicationSet CRDs, wired together through the knowledge graph, instead of Kunobi-computed synthetic resources. The views look and behave the same; if you scripted against the old virtual kunobi.ninja kind names, they no longer exist.
• Cross-cluster ArgoCD relationships — ArgoCD Applications that manage resources on a different cluster are now correctly related through the knowledge graph, using the server URL recorded on the Application to join across clusters.
• Git-provider access explains itself — in the Member → Repositories drilldown, each repository now shows why the person can reach it (a direct grant, a team or group, or an org role / account ownership), and overlapping paths resolve to the most specific reason. Bitbucket workspace ownership and per-group roles that the backend already knew now render as columns across GitHub, GitLab and Bitbucket.
• Sharper "did you know" tips — feature-discovery tips are now ordered by importance, surface on the home screen, and include a tip about connecting an MCP client.
• Clearer terms acceptance — Kunobi records your acceptance of the EULA and privacy policy against the exact document versions you saw, and shows a notice when those documents are updated.

Bug Fixes

• Kubernetes table columns behave — column visibility is only auto-seeded when a table genuinely overflows, stored column choices are kept when a table's column set is still empty, drilled tables key their column state off the view actually rendered, and the namespace filter now survives changing the kind you're viewing. Clearing a selection also closes the action bar and sidebar as expected.
• Cloudflare fixes — DNS record priority is now sent on update, the status column reflects real connection state, testing a stored token works, and fan-out errors are surfaced instead of swallowed.
• Bare-metal and storage source fixes — Redfish applies the profile's event count when fetching the system event log and drops its cached client when the certificate policy changes; Ceph marks a connection's name immutable so edits stop being silently discarded; SNMP hosts report a healthy status dot when online and keep host/port read-only on edit.
• Agent Gateway edit safety — Test actions no longer mutate state and validate their target, editing an MCP target no longer deletes secrets you didn't mention, and gateway state mutations are atomic with the existing config preserved if a load fails.
• Graph card polish — far-zoomed cards render Kunobi's brand identity, and the mouse wheel zooms as expected inside graph views.
• Source sidebar stability — the source detail sidebar no longer resets its active tab when polling refreshes the underlying rows, and connect / disconnect reflects live status immediately.

Installation

This is an unstable release. To try it on Homebrew or winget, use the unstable identifiers:

brew install --cask kunobi-unstable

winget install kunobi-ninja.kunobi.Unstable

Existing installs on the stable channel are unaffected. You can also log in and download the unstable build directly, or update from within an existing unstable install.

Feedback

We'd love to hear your thoughts!