kiroBackend implements Backend by spawning `kiro-cli acp` and communicating via the standard ACP JSON-RPC 2.0 transport over stdin/stdout. Kiro CLI advertises loadSession, returns models from session/new, and supports session/set_model, so the existing Hermes/Kimi ACP client can drive it with only
| 33 | // session/set_model, so the existing Hermes/Kimi ACP client can drive it with |
| 34 | // only provider-specific launch and tool-name normalization. |
| 35 | type kiroBackend struct { |
| 36 | cfg Config |
| 37 | } |
| 38 | |
| 39 | func (b *kiroBackend) Execute(ctx context.Context, prompt string, opts ExecOptions) (*Session, error) { |
| 40 | execPath := b.cfg.ExecutablePath |
nothing calls this directly
no outgoing calls
no test coverage detected