Home Verkennen Help
Inloggen
AI
/
kilocode
spiegel van https://github.com/Kilo-Org/kilocode.git
2
0
Vork 0
Bestanden Issues 0 Wiki
Aftakking: mark/debounce
Aftakkingen Labels
kilocode
/
cli
/
CHANGELOG.md

CHANGELOG.md 17 KB
Permalink Geschiedenis Ruwe

@kilocode/cli

0.3.0

Minor Changes

  • #3623 ef6bcac Thanks @Sureshkumars! - # Checkpoint Restore

    Allows users to restore their conversation to a previous point in time.

    What do we have here?

    View your checkpoints

    /checkpoint list

    This shows all available restore points with: Hash for the checkpoint When it was created

    Restore to a checkpoint

    /checkpoint restore abc123...

    You'll see a confirmation showing: Which checkpoint you're going back to How many messages will be removed What will happen to your current work

    Choose Restore to go back, or Cancel to keep working.

    Example

    Let's say you asked Kilo CLI to refactor some code, but you don't like the result:

    Run /checkpoint list to see earlier save points

    Find the checkpoint from before the refactoring

    Run /checkpoint restore <hash> with that checkpoint's hash

    Confirm the restore Your conversation is now back to before the refactoring happened

    Why use checkpoints?

    1. Undo mistakes - Go back if something went wrong
    2. Try different approaches - Restore and try a different solution
    3. Keep working states - Return to a point where everything was working

Patch Changes

  • #3500 2e1a536 Thanks @iscekic! - improves windows support

  • #3641 94bc43a Thanks @KrtinShet! - Fix workspace path resolution when using relative paths with --workspace flag. Bash commands now execute in the correct directory.

0.2.0

Minor Changes

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

  • #3452 127a255 Thanks @Sureshkumars! - This PR improves the display of MCP tool requests and responses in the CLI, addressing issues with truncated payloads, poor formatting, and lack of metadata.

    • MCP request arguments were difficult to read (no formatting, no preview mode)
    • MCP response payloads were displayed as raw text dumps, overwhelming the terminal
    • No JSON detection or pretty-printing
    • No metadata about content size or type
    • Missing error handling for malformed data
    • No indication when content is truncated/previewed

    Created new SayMcpServerResponseMessage component for MCP responses and refactored AskUseMcpServerMessage to share formatting logic. Both will make use of newly added utility functions for JSON detection, formatting, and metadata display. formatContentWithMetadata() - Detects JSON, formats it, handles preview logic (>20 lines → show 5) formatJson() - Pretty-prints JSON with configurable indentation approximateByteSize() - Estimates byte size using str.length * 3 formatByteSize(), buildMetadataString() - Display helpers

    before after
    before after

    Run the KiloCode CLI and let it automatically use any configured MCP server.

Patch Changes

0.0.16

Patch Changes

0.0.15

Patch Changes

0.0.14

Patch Changes

  • #3371 e0e01b2 Thanks @RSO! - Add a --json flag to render a stream of JSON objects while in --auto mode

0.0.13

Patch Changes

0.0.12

Patch Changes

  • #3352 c89bd23 Thanks @Sureshkumars! - MCP operations were being auto-rejected in CI mode (autonomous mode) even when autoApproval.mcp.enabled: true, breaking GitHub Actions workflows and other autonomous operations that rely on MCP servers.

    Root Cause: The extension sends MCP requests with the ask type set to the operation name (e.g., "use_mcp_server", "access_mcp_resource"), but the approval decision logic only handled these as tool names within the "tool" ask type. This caused MCP requests to fall through to the default case and get auto-rejected.

    The approval decision service uses a switch statement on askType to determine whether to auto-approve, auto-reject, or require manual approval:

    switch (askType) {
    case "tool": // handles tool names like "readFile", "writeFile"
    case "command": // handles command execution
    case "followup": // handles followup questions
    case "api_req_failed": // handles retry requests
    default: // ❌ MCP ask types fell here → auto-reject
}

    Added explicit cases for MCP ask types to the switch statement:

    case "use_mcp_server":
case "access_mcp_resource":
    if (config.mcp?.enabled) {
        return { action: "auto-approve" }
    }
    return isCIMode ? { action: "auto-reject", ... } : { action: "manual" }

    Also enhanced the tool handler to catch MCP operations sent as tool names (in case the extension changes format):

    if (tool === "use_mcp_tool" || tool === "use_mcp_server" || tool === "access_mcp_resource") {
    if (config.mcp?.enabled) {
        return { action: "auto-approve" }
    }
    // ... rejection logic
}
    • Chose explicit ask type handling over mapping ask types to tool names (cleaner, respects extension's message format)
    • Kept both ask type and tool name handlers for defense-in-depth (minimal overhead, prevents future breakage)
    • Removed verbose logging to reduce noise while maintaining troubleshooting capability
    before after
    MCP operations auto-rejected in CI mode with error "Auto-rejected in CI mode" MCP operations auto-approved when autoApproval.mcp.enabled: true
    before-the-fix after-the-fix
    1. Just kilocode --auto "Review the PR #2 in X/X repo, use github mcp servers if needed"
    2. Configure MCP settings with GitHub MCP server

    3. Set autoApproval.mcp.enabled: true in config

      cat > ~/.kilocode/cli/config.json <<EOF
{
"version": "1.0.0",
"autoApproval": {
"mcp": {
  "enabled": true
}
}
}
EOF

`kilocode --auto "Review the PR #2 in X/X repo, use github mcp servers if needed"`

0.0.11

Patch Changes

  • #3278 cba3d00 Thanks @catrielmuller! - Improved stability of the approval menu, preventing it from showing when you don't expect it

0.0.10

Patch Changes

0.0.9

Patch Changes

0.0.8

Patch Changes

0.0.7

Patch Changes

0.0.6

Patch Changes

0.0.5

Patch Changes

0.0.4

Patch Changes

  • #3066 263741a Thanks @RSO! - Made Logo responsive so that it better fits smaller screens

0.0.3

Patch Changes