polydev-ai 1.8.37 → 1.8.38
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/mcp/README.md +18 -0
- package/package.json +1 -1
package/mcp/README.md
CHANGED
|
@@ -195,6 +195,24 @@ This error occurs when the MCP handshake fails. Common causes and fixes:
|
|
|
195
195
|
2. Check authentication: `claude auth status` / `codex login status`
|
|
196
196
|
3. Enable debugging: `export POLYDEV_CLI_DEBUG=1`
|
|
197
197
|
|
|
198
|
+
### Gemini CLI: Truncated "I will search..." Responses
|
|
199
|
+
|
|
200
|
+
If Gemini CLI returns truncated responses like "I will search for..." or "I will look up..." instead of actual analysis:
|
|
201
|
+
|
|
202
|
+
**Cause**: Gemini CLI has an "agentic mode" that triggers when prompts mention code, files, or repositories. In headless `-p` mode, Gemini tries to use tools (file search, web search) but they can't execute, so it outputs intentions instead of analysis.
|
|
203
|
+
|
|
204
|
+
**Fix**: The `-s` (sandbox) flag disables tool use. As of v1.8.37, polydev-ai automatically adds this flag. To update:
|
|
205
|
+
|
|
206
|
+
```bash
|
|
207
|
+
# Update polydev-ai
|
|
208
|
+
npm update -g polydev-ai
|
|
209
|
+
|
|
210
|
+
# Or in mcp-execution
|
|
211
|
+
cd ~/mcp-execution && npm update polydev-ai
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
**Note**: Simple prompts (like "What is 5 + 5?") work correctly because they don't trigger agentic behavior. Complex prompts about code/repositories do.
|
|
215
|
+
|
|
198
216
|
### Token Issues
|
|
199
217
|
|
|
200
218
|
1. Verify your token at [polydev.ai/dashboard](https://polydev.ai/dashboard)
|
package/package.json
CHANGED