login

Sign the Greptile CLI in to the user's Greptile account.

Tell the user a browser window will open and that they need to finish signing in there, then run:

GREPTILE_NO_UPDATE_CHECK=1 node "${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs" login

Outside Claude Code (Codex), replace ${CLAUDE_PLUGIN_ROOT} with the plugin root: the absolute path two folders above this SKILL.md.

Give the Bash call a 600000 ms timeout. The CLI waits up to ten minutes for the browser round-trip to complete, far longer than the two-minute default.

This opens auth.greptile.com and completes an OAuth flow. It signs in the CLI, which keeps its own credentials in ~/.greptile/auth.json.

The greptile MCP server in this plugin authenticates separately, through Claude Code's own /mcp menu — same Greptile account, same OAuth provider, and the same audience, but a separate token store. A user who wants both surfaces signs in twice, and signing in here does not authenticate the MCP server (or the reverse).

If the user wanted MCP tools rather than the CLI, point them at /mcp instead.