kiro-rs

The kiro-rs project is organized into several core functional modules:

• src/anthropic/: Provides an Anthropic API compatibility layer, including routing, request handlers, authentication middleware, and protocol converters.
• src/kiro/: Contains the core Kiro API client logic, including provider management, token management, machine ID generation, and an AWS Event Stream parser for streaming responses.
• src/admin/: Implements the Admin API module with its own routing, handlers, and business logic services.
• src/admin_ui/: Handles the routing for embedded static files from the Admin UI.
• admin-ui/: The frontend source for the Admin UI; its build artifacts are embedded directly into the final binary.
• src/model/: Defines application configuration and command-line argument models.
• config.example.json: A template for the required configuration file.

The credentials.json file stores authentication tokens. It supports both a single object (legacy) and an array of objects (multi-credential mode). Multi-credential mode enables automatic failover and automatic writing of refreshed tokens back to the file.

Multi-credential features:

• Priority: Credentials are sorted by the priority field (lower numbers have higher priority; default is 0).
• Failover: If a credential fails, the service automatically tries the next available one. The service performs up to 3 retries per credential and up to 9 retries per request.
• Auth Method: Use authMethod: "idc" for IdC, Builder-ID, or IAM login types.

Credential-level Overrides: Credentials can override global config.json settings for region, authRegion, apiRegion, and proxyUrl. Setting proxyUrl: "direct" explicitly disables proxies for that specific credential.

[
   {
      "refreshToken": "第一个凭据的刷新token",
      "expiresAt": "2025-12-31T02:32:45.144Z",
      "authMethod": "social",
      "priority": 0
   },
   {
      "refreshToken": "第二个凭据的刷新token",
      "expiresAt": "2025-12-31T02:32:45.144Z",
      "authMethod": "idc",
      "clientId": "xxxxxxxxx",
      "clientSecret": "xxxxxxxxx",
      "region": "us-east-2",
      "priority": 1,
      "proxyUrl": "socks5://proxy.example.com:1080",
      "proxyUsername": "user",
      "proxyPassword": "pass"
   },
   {
      "refreshToken": "第三个凭据（显式不走代理）",
      "expiresAt": "2025-12-31T02:32:45.144Z",
      "authMethod": "social",
      "priority": 2,
      "proxyUrl": "direct"
   }
]

Kiro uses an abstraction layer to handle different service endpoints (such as ide or cli) that share common logic like credential pooling, token refreshing, and retry mechanisms but differ in their URLs, headers, and request bodies.

• KiroEndpoint: An abstraction that defines how a specific endpoint handles its unique requirements, such as its API/MCP URLs, header decoration, and body transformations.
• KiroProvider: Manages a registry of these endpoints. It selects the correct KiroEndpoint implementation at runtime based on the endpoint field found in the user's credentials or the config.defaultEndpoint setting.

This architecture allows the system to seamlessly switch between different service implementations while maintaining a unified request lifecycle.

/// Kiro 端点
///
/// 同一个 `KiroProvider` 可持有多个 endpoint 实现，按凭据级字段切换。
pub trait KiroEndpoint: Send + Sync {
    // ...
}

The AWS Event Stream protocol supports 10 specific value types. When parsing, these are represented by the HeaderValueType enum and mapped to the HeaderValue enum: