feat(plugins): use harness setup across agent hosts - #15
Conversation
![glean-it[bot]](https://avatars.githubusercontent.com/u/48140418?s=60&v=4){kind=small}
| ``` | ||
|
|
||
| Before starting Codex, connect the MCP server used by the plugin you installed: | ||
| Before starting Codex, set up Glean by prompting the harness, for example: |
There was a problem hiding this comment.
Issue: The setup instructions tell users to prompt the harness before starting Codex, but the harness must be running to receive the prompt.
Suggested fix: Start Codex first, prompt the harness to set up Glean, complete OAuth, then start a new Codex task.
🔧 Tag @ glean-for-engineering to fix or click here to fix in Glean
💬 Help us improve! Was this comment helpful? React with 👍 or 👎
There was a problem hiding this comment.
Fixed in 821a894. The Codex marketplace README now tells users to start Codex first, prompt the harness to set up Glean, complete OAuth, and only then start a new Codex task.
— sent via Glean Pi
|
|
||
| Then start a new Codex task so the bundled skills and MCP tools are available. | ||
| The **Glean developer docs** plugin uses a separate public MCP server. Run | ||
| `codex mcp add glean-dev-docs --url https://developers.glean.com/mcp` if you |
There was a problem hiding this comment.
Issue: The developer-docs MCP server is added after the documented task restart, with no subsequent restart, so its tools may not be available in the current Codex task.
Suggested fix: Run the codex mcp add command before restarting, or explicitly instruct users to start another Codex task afterward.
🔧 Tag @ glean-for-engineering to fix or click here to fix in Glean
💬 Help us improve! Was this comment helpful? React with 👍 or 👎
There was a problem hiding this comment.
Fixed in 821a894. The developer-docs MCP command now appears before the documented new-task restart, followed by an explicit instruction to start a new Codex task so its tools are available.
The developer-docs guidance remains in this file because overrides/codex/root/README.md is the marketplace-level README for both the glean and glean-dev-docs plugins; the plugin-specific READMEs remain separate.
— sent via Glean Pi
| - [Codex](https://developers.openai.com/codex) with plugin support | ||
| - A Glean account with MCP access | ||
| - Your Glean MCP server URL and server name | ||
| - A Glean account with MCP access |
There was a problem hiding this comment.
Fixed in 821a894 by removing the duplicate Glean MCP access requirement bullet.
— sent via Glean Pi
eshwar-sundar-glean
changed the title
2 participants
Summary
connect-gleanskill from Claude Code, Codex, and Cursor.Set up Glean for me.Target behavior
connect-gleanUpdated the shared skill guidance (
using-glean,project-handoff, and skill creation) so missing Glean tools direct the user to prompt the harness instead of referencingconnect-glean.Historical changelog entries remain unchanged.
Verification
npm test— build and validation passed for Claude, Cursor, and Codexconnect-gleanreferences in any generated targetgit diff --checkpassed