Moving from Kiro CLI or Amazon Q

Kiro CLI, Amazon Q, and Fig wrap your shell in their own terminal program, as Pacer does with pacer-term. With two of them set up, every keystroke goes through both, and two popovers compete for the same line. Remove the old one before you rely on Pacer.

1. Remove its shell blocks

Run kiro-cli integrations uninstall dotfiles, or q integrations uninstall dotfiles for Amazon Q. If it says "Not installed" while the blocks are still there, Pacer's block sits above them and the tool no longer recognizes its own. Then delete them by hand: the # Kiro CLI pre block and # Kiro CLI post block lines, and the line after each, in ~/.zshrc, ~/.zprofile, ~/.bashrc, and ~/.bash_profile.

2. Quit it

Run kiro-cli quit or q quit.

3. Close old tabs

Tabs you opened before step 1 still run inside the old wrapper. Close them, and open new ones.

4. Check with pacer doctor

Run pacer doctor. Its Other tools check names any blocks that are left and counts the shells still inside the old wrapper.

Doing step 1 before you set up Pacer avoids the "Not installed" case, because the old tool's block is still the first one in each file.

The popover works the same way, from the same Fig spec library, in Ghostty, iTerm2, or Terminal. You lose the AI chat and agents, and you gain changed files first, branches with their last commit, ranking by repo, the risky command guard, pacer stats, and pacer doctor. Compare them on the Amazon Q page.