[jschatz1]

Removes kai connect, the terminal entry point to the Gmail, Calendar, Drive, Dropbox, Notion and Slack connectors.

The server side is removed in kaicontext/kai-server (connectors endpoints and the Composio broker). Over the last 30 days the load-balancer logs show no connect, execute or send calls, only 15 list calls. Composio is a High-risk vendor that holds users' OAuth tokens.

go build ./cmd/kai and go vet ./cmd/kai pass.

🤖 Generated with Claude Code

---

Kai context

_{Written by Kai from the change itself. Kai only edits this section; everything above it is the author's.}

Deletes cmd/kai/connect.go, removing the kai connect command and all of its supporting code.

Changes

• Removes the connectCmd cobra command and its init() registration from rootCmd, eliminating the kai connect [provider] terminal entry point
• Deletes the runConnect function, which handled listing connectors, initiating OAuth connections, disconnecting accounts, and polling for consent completion
• Deletes the connectList helper that queried GET /api/v1/connectors and printed provider, status, and email
• Deletes the connectorStatus helper that polled the connectors list to watch a specific link ID during the consent flow
• Deletes the connectorAPI helper that made authenticated HTTP requests to the /api/v1/connectors server endpoints
• Removes the --disconnect and --account command-line flags and the connectPollInterval/connectPollBudget constants

[kaicontext]

Kai review · Ready to merge (9/10)

Read the whole thing — it does what it says, and nothing jumped out at me.

Next: merge when your checks are green — I found nothing to fix.

To get to 10/10

• −1 · add or update a test: cmd/kai/connect.go changed and no test did

Important files changed

File	Change
cmd/kai/connect.go	modified · +0 −218

How I reviewed it — 1 file, 7 turns, 19s

A clean, self-contained deletion of kai connect with no dangling references anywhere in kaicontext/kai-cli; the server-side half in kaicontext/kai-server is outside this review's boundary.

What I opened

• cmd/kai/connect.go

Full read-through

The file is gone from the working tree (it was deleted), and its full 218-line content was already in the diff I reviewed. I've re-read that content against my sweep: the deleted symbols (connectCmd, runConnect, connectList, connectorStatus, connectorAPI, connectDisconnect, connectAccount), the /api/v1/connectors endpoint paths, and the init() registration are all self-contained to this file, and my earlier grep confirmed none are referenced elsewhere in kaicontext/kai-cli. Nothing in the deleted file changes my findings.

Review

I reviewed kaicontext/kai-cli at the commit that deletes cmd/kai/connect.go. I could not read the server-side companion change in kaicontext/kai-server (the /api/v1/connectors endpoints and Composio broker the author says are being removed in parallel), so the coordination between the two halves is outside my view.

This is a clean removal. The deleted file was self-contained: it owned the connectCmd cobra command, its two flags (connectDisconnect, connectAccount), the init() that registered it on rootCmd, and all four helpers (runConnect, connectList, connectorStatus, connectorAPI). Within kaicontext/kai-cli nothing else referenced any of those symbols, the /api/v1/connectors path, or the word "connectors"; there is no dangling test, completion, or help reference. The remote package it imported is still used widely elsewhere, so no import is stranded. There are no defects to report in this repo.

The one thing worth saying back to the author is a coordination note, not a defect in this code: the CLI's kai connect is gone, so any user who still runs it gets cobra's standard "unknown command" rather than a tailored retirement message. If the server endpoints are removed in the same deploy window that's fine; if the CLI ships before the server, a user on an older CLI binary hitting the removed endpoints would get a 404 — but that's about rollout sequencing between the two repos, which I can't see here, not about this change.

Merge-ready as far as this repo is concerned.

_{Size M · Risk S · +0 −218 · 1 file · reaches 0 · the full analysis · Reply to any of my comments and I'll answer, or say @kaicontext anywhere on this PR — a question, or "take another look at the retry logic".}