Enables Entire CLI checkpoints, rewind, and transcript capture for Kiro coding sessions. Once installed, Entire automatically tracks your Kiro sessions — creating checkpoints on commits and capturing transcripts for review.
- Entire CLI installed and on
PATH - Kiro (IDE or
kiro-cli-chatCLI) installed - Go 1.26+ (to build from source)
cd agents/entire-agent-kiro
make buildThis produces ./entire-agent-kiro in the current directory.
cp ./entire-agent-kiro ~/.local/bin/Or use Go install:
go install ./cmd/entire-agent-kiroentire-agent-kiro infoThis should print JSON describing the agent's capabilities.
cd /path/to/your/project
entire enableentire-agent-kiro are-hooks-installedShould return {"installed": true}.
Entire will now automatically capture checkpoints and transcripts during your Kiro sessions.
When you run entire enable --agent kiro, the agent installs hooks in three locations:
| Location | Purpose |
|---|---|
.kiro/agents/entire.json |
Agent configuration for Kiro CLI |
.kiro/hooks/*.kiro.hook |
Lifecycle hooks (start, stop, commit) |
.vscode/settings.json |
Trusted command entry for Kiro IDE |
During a session, these hooks fire on lifecycle events (session start, stop, commit), allowing Entire to create checkpoints and capture what the AI agent did.
| Capability | Supported | Description |
|---|---|---|
hooks |
Yes | Installs and manages Kiro lifecycle hooks |
transcript_analyzer |
Yes | Extracts modified files, prompts, and summaries from transcripts |
transcript_preparer |
No | — |
token_calculator |
No | — |
text_generator |
No | — |
hook_response_writer |
No | — |
subagent_aware_extractor |
No | — |
All subcommands required by the external agent protocol:
Core: info, detect, get-session-id, get-session-dir, resolve-session-file, read-session, write-session, format-resume-command
Hooks: parse-hook, install-hooks, are-hooks-installed, uninstall-hooks
Transcript: read-transcript, chunk-transcript, reassemble-transcript, get-transcript-position, extract-modified-files, extract-prompts, extract-summary
make build # Build the binary
make test # Run unit tests
make clean # Remove built binary
# Run directly without installing:
go run ./cmd/entire-agent-kiro infoE2E tests live in the shared e2e/ directory at the repo root (not inside this agent's directory). The harness auto-discovers and builds all agents, then runs tests against each.
Exercise each protocol subcommand directly — no external dependencies needed:
- Identity:
info,detect(present/absent) - Sessions:
get-session-id,get-session-dir,resolve-session-file,write-session/read-sessionround-trip - Transcript:
read-transcript,chunk-transcript/reassemble-transcriptround-trip - Hooks:
parse-hook(spawn, prompt-submit, pre-tool-use, stop),install-hooks/uninstall-hooks/are-hooks-installed, idempotent install - Transcript analysis:
get-transcript-position,extract-modified-files,extract-prompts,extract-summary - Other:
format-resume-command, unknown subcommand handling
Full integration tests requiring entire CLI and kiro-cli-chat:
- SinglePromptManualCommit — agent creates file → commit → checkpoint with trailer
- MultiplePromptsManualCommit — two prompts → single commit → checkpoint covers both
- DetectAndEnable —
entire enablesucceeds when.kiro/exists - HooksInstalledAfterEnable —
are-hooks-installedconfirms hooks after enable - RewindPreCommit — create file A → checkpoint → create file B → rewind → B is gone
- RewindAfterCommit — two commits → rewind to first → second file is gone
- SessionPersistence — session file created in
.entire/tmp/after prompt
# From the repo root:
make test-e2e # All E2E tests (lifecycle tests skip if deps missing)
make test-e2e-lifecycle # Lifecycle tests only (fails if deps missing)
# Run a specific test:
cd e2e && go test -tags=e2e -v -count=1 -run TestKiro_Info ./...Agent not discovered by Entire
- Verify the binary is on your
PATH:which entire-agent-kiro - Check detection:
entire-agent-kiro detect(requiresENTIRE_REPO_ROOTto be set)
Hooks not firing
- Verify
.kiro/agents/entire.jsonexists in your project - Check that
.kiro/hooks/contains*.kiro.hookfiles - For Kiro IDE: verify
.vscode/settings.jsonhas the trusted command entry
IDE vs CLI differences
- Kiro IDE uses VS Code's trusted command mechanism — hooks fire via
.vscode/settings.json - Kiro CLI (
kiro-cli-chat) reads hooks directly from.kiro/hooks/ - Both paths are configured by
install-hooks
This agent implements the Entire external agent protocol.