← GreptileCONTENT HISTORY
WHAT CHANGED
changed
changed
changed
Update to Greptile
Snapshot Oct 28, 2026 · 12:24 UTC · version 1.3.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for login
Full description — Now says: Sign the Greptile CLI in to your Greptile account
Observed in instructions or declared skills. Runtime behavior has not been tested.
Save Greptile and check future changes in Following.
Up to 10 plugins free · no card required.
All fields and original values.
Full description
Before
Sep 30, 2026 · 23:08 UTC
Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI.
After
Oct 28, 2026 · 12:24 UTC
Sign the Greptile CLI in to your Greptile account
Skill instructions
Before
Sep 30, 2026 · 23:08 UTC
bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI. Sign the bundled Greptile CLI in to the user's account. Tell the user that a browser will open and they need to finish signing in there. Resolve `...
After
Oct 28, 2026 · 12:24 UTC
Greptile CLI in to your Greptile account metadata: internal: true allowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs:*) Sign the Greptile CLI in to the user's Greptile account. Tell the user a browser window will open ...
Supporting files
Before
Sep 30, 2026 · 23:08 UTC
[{"relative_path":"scripts/greptile.mjs","size_in_bytes":10697706},{"relative_path":"scripts/greptile.version","size_in_bytes":6}]
After
Oct 28, 2026 · 12:24 UTC
[]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,24 +1,33 @@ --- name: login -description: Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI. +description: Sign the Greptile CLI in to your Greptile account +metadata: + internal: true +allowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs:*) --- -Sign the bundled Greptile CLI in to the user's account. Tell the user that a -browser will open and they need to finish signing in there. +Sign the Greptile CLI in to the user's Greptile account. -Resolve `<skill-root>` as the directory containing this `SKILL.md`. -Substitute that absolute path in the command; use the bundled script rather -than a separately installed `greptile` executable. +Tell the user a browser window will open and that they need to finish signing +in there, then run: -```sh -GREPTILE_NO_UPDATE_CHECK=1 node "<skill-root>/scripts/greptile.mjs" login ``` +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`. -Allow up to ten minutes for the browser round-trip. If the shell tool returns -a running session, keep polling that session until login finishes. +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). -This opens `auth.greptile.com` and saves CLI credentials in -`~/.greptile/auth.json`. The plugin's MCP connection authenticates separately -through Codex and keeps its own tokens. Signing in to one does not sign in to -the other. If the user wants MCP access, direct them to connect the Greptile -MCP server in Codex instead. +If the user wanted MCP tools rather than the CLI, point them at `/mcp` instead.
Full technical diff · 3 changed fields
changed /description
BEFORE
"Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI."
AFTER
"Sign the Greptile CLI in to your Greptile account"
changed /included_files
BEFORE
[
{
"relative_path": "scripts/greptile.mjs",
"size_in_bytes": 10697706
},
{
"relative_path": "scripts/greptile.version",
"size_in_bytes": 6
}
]AFTER
[]
changed /skill_md_contents
BEFORE
"---\nname: login\ndescription: Sign the bundled Greptile CLI in through browser OAuth when the user wants to authenticate the CLI.\n---\n\nSign the bundled Greptile CLI in to the user's account. Tell the user that a\nbrowser will open and they need to finish signing in there.\n\nResolve `<skill-root>` as the directory containing this `SKILL.md`.\nSubstitute that absolute path in the command; use the bundled script rather\nthan a separately installed `greptile` executable.\n\n```sh\nGREPTILE_NO_UPDATE_CHECK=1 node \"<skill-root>/scripts/greptile.mjs\" login\n```\n\nAllow up to ten minutes for the browser round-trip. If the shell tool returns\na running session, keep polling that session until login finishes.\n\nThis opens `auth.greptile.com` and saves CLI credentials in\n`~/.greptile/auth.json`. The plugin's MCP connection authenticates separately\nthrough Codex and keeps its own tokens. Signing in to one does not sign in to\nthe other. If the user wants MCP access, direct them to connect the Greptile\nMCP server in Codex instead.\n"
AFTER
"---\nname: login\ndescription: Sign the Greptile CLI in to your Greptile account\nmetadata:\n internal: true\nallowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs:*)\n---\n\nSign the Greptile CLI in to the user's Greptile account.\n\nTell the user a browser window will open and that they need to finish signing\nin there, then run:\n\n```\nGREPTILE_NO_UPDATE_CHECK=1 node \"${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs\" login\n```\n\nOutside Claude Code (Codex), replace `${CLAUDE_PLUGIN_ROOT}` with the plugin\nroot: the absolute path two folders above this `SKILL.md`.\n\nGive the Bash call a **600000 ms timeout**. The CLI waits up to ten minutes for\nthe browser round-trip to complete, far longer than the two-minute default.\n\nThis opens `auth.greptile.com` and completes an OAuth flow. It signs in the\n**CLI**, which keeps its own credentials in `~/.greptile/auth.json`.\n\nThe `greptile` MCP server in this plugin authenticates separately, through\nClaude Code's own `/mcp` menu — same Greptile account, same OAuth provider,\nand the same audience, but a separate token store. A user who wants both\nsurfaces signs in twice, and signing in here does not authenticate the MCP\nserver (or the reverse).\n\nIf the user wanted MCP tools rather than the CLI, point them at `/mcp` instead.\n"Full snapshot data
{
"description": "Sign the Greptile CLI in to your Greptile account",
"included_files": [],
"name": "login",
"skill_md_contents": "---\nname: login\ndescription: Sign the Greptile CLI in to your Greptile account\nmetadata:\n internal: true\nallowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs:*)\n---\n\nSign the Greptile CLI in to the user's Greptile account.\n\nTell the user a browser window will open and that they need to finish signing\nin there, then run:\n\n```\nGREPTILE_NO_UPDATE_CHECK=1 node \"${CLAUDE_PLUGIN_ROOT}/scripts/greptile.mjs\" login\n```\n\nOutside Claude Code (Codex), replace `${CLAUDE_PLUGIN_ROOT}` with the plugin\nroot: the absolute path two folders above this `SKILL.md`.\n\nGive the Bash call a **600000 ms timeout**. The CLI waits up to ten minutes for\nthe browser round-trip to complete, far longer than the two-minute default.\n\nThis opens `auth.greptile.com` and completes an OAuth flow. It signs in the\n**CLI**, which keeps its own credentials in `~/.greptile/auth.json`.\n\nThe `greptile` MCP server in this plugin authenticates separately, through\nClaude Code's own `/mcp` menu — same Greptile account, same OAuth provider,\nand the same audience, but a separate token store. A user who wants both\nsurfaces signs in twice, and signing in here does not authenticate the MCP\nserver (or the reverse).\n\nIf the user wanted MCP tools rather than the CLI, point them at `/mcp` instead.\n"
}SHA-256 of public snapshot: ac7fe04be95f964d6a131bbd340e2fcc2def46e1eb18b84b12a1895666c8bdbf