Repository navigation
Chat with your own Kiro plan, and fall back between chats - #155
Open
betodoescher wants to merge 4 commits into
Open
betodoescher wants to merge 4 commits into
betodoescher wants to merge 4 commits into
Conversation
Cursor has no public chat API, and calling its private endpoints is against its terms. The supported way is the Cursor CLI: sign in once with `agent login`, then each chat turn runs `agent -p --output-format json --mode ask --trust --model <m>`, resuming the same session for the next turns. - Read-only (`--mode ask`), in an empty private folder under the local data directory, so the agent has nothing of the user's to read. The folder is always the same because `--resume` is scoped to it. - 120 s timeout, the child is killed on drop. An optional API key goes through CURSOR_API_KEY in the environment (never argv) and lives in the Secret Service / Credential Manager like every other key. - Text files ride along inline on the first turn; images and PDFs say they are not supported with Cursor yet. Settings -> Cursor: "Chat answers with" Claude (API key) or Cursor (your plan), the model list from `agent models`, sign-in status from `agent status`, a "Sign in with Cursor" button and the optional key. Claude stays the default. Co-authored-by: Cursor <cursoragent@cursor.com>
…acks it Co-authored-by: Cursor <cursoragent@cursor.com>
…and settings Co-authored-by: Cursor <cursoragent@cursor.com>
Adds the Kiro CLI as a chat provider next to Cursor and the Claude API: `kiro-cli chat --no-interactive --trust-tools=` (no tools, answers only) in a private folder, with `--resume` from the second turn. The text output is used because stream-json needs the v2 engine, which does not resume yet. Settings -> Chat now turns each provider on or off. The turned-on ones are tried in order (Cursor, Kiro, then the API) until one answers, so running out of credits on one plan hands the chat to the next. A Kiro section shows the CLI status and models, and the island shows a Kiro dot next to Cursor. Co-authored-by: Cursor <cursoragent@cursor.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
kiro-cli chat --no-interactive --trust-tools=(no tools, answers only) in a privatefolder,
--resumefrom the second turn. Text output, becausestream-jsonneeds thev2 engine, which does not resume conversations yet.
turned-on ones are tried in that order until one answers — out of credits on Cursor,
Kiro takes over. Each keeps its own conversation.
--list-models), install /kiro-cli loginhint.~/.local/bin, prompt building and ANSI stripping are shared with Cursor.Testing
kiro-cli2.20.1 signed in: multi-turn chat keeps context, model switch,fallback from Cursor to Kiro.
cargo test -p coucou(Kiro answer/error parsing, model list),tsc --noEmit.Made with Cursor