Mikie / Field notes

Set up Mikie with Claude Code or Codex

Install the CLI, connect your coding client, and verify one focused task in your own repository.

How-to5 min read
Select relevant code from a repository, then use it for a focused coding task.REPOSITORYFOCUSED TASK
Less to read. More to work with.

1. Install the Mikie CLI

You need Node.js 22 or newer on Windows x64, macOS on Apple Silicon or Linux x64. This always installs the latest version:

bash
npm install -g @getmikie/cli@latest

On Windows, if PowerShell says running scripts is disabled, use npm.cmd install -g @getmikie/cli@latest instead.

2. Sign in

Your browser opens. Allow the connection, then come back to the terminal:

bash
mikie login

Want to see what Mikie can read in a project first? Run mikie privacy review.

3. Add Mikie to your client

Pick the client you use:

bash
mikie setup claude   # Claude Code
mikie setup codex    # Codex

Setup backs up your existing client configuration, adds only Mikie's own entries and leaves your other MCP servers alone.

4. Open your project

Open Claude Code or Codex in your project folder and work as usual. Mikie connects that project automatically; there is nothing else to run.

5. Check it works

One command checks sign-in, the project connection and the tools your client sees:

bash
mikie doctor

If it reports that your sign-in expired, run mikie login again and then mikie doctor.

Other MCP clients

Claude Code and Codex have setup commands. Any other MCP client can launch Mikie with the command mikie mcp; the docs show the config. Mikie doesn't test or support each of those clients one by one.

Not ready to change anything yet? Start in shadow mode and see the projected savings first.

Start with a first task you can verify

Choose a small defect with a known failing test or one change with a clear before-and-after behavior. Keep your existing client permissions and project instructions in place, then confirm that the installed integration is available in the client you actually use.

First-task prompt
Fix this reproducible failure: [paste the error].
Expected behavior: [describe the result].
Start at: [relevant source and test].
Keep the change scoped. Run the acceptance check.
Report changed files, test result, and anything still unverified.

Troubleshoot the connection before repeating the work

If the browser sign-in finishes but the client still cannot connect, rerun mikie doctor in the same project folder. Confirm you configured the client you launched and reopen it if its configuration has changed. Keep the diagnostic error visible instead of repeatedly reinstalling.

  • Sign-in expired: run mikie login, then rerun the diagnostic.
  • Wrong client configured: use the matching setup command and verify its tools.
  • Wrong project open: switch to the intended repository and check the connection there.
  • Unexpected usage: check the billing method and receipt label before calling it a cost increase or saving.

Sources: Commands are from the installed Mikie CLI's public help and the Mikie docs.

Try it on your own repository.

Give your agent the context it needs, then see how your next session compares.