Skip to content

docs: clarify enhance_prompt browser and OpenCode usage#15

Merged
missdeer merged 3 commits into
masterfrom
codex/fix-issue-#10
Mar 23, 2026
Merged

docs: clarify enhance_prompt browser and OpenCode usage#15
missdeer merged 3 commits into
masterfrom
codex/fix-issue-#10

Conversation

@missdeer

Copy link
Copy Markdown
Owner

Motivation

  • Users (and agent-style clients like OpenCode) were confused when enhance_prompt appeared to hang after the MCP tool call because the tool by default opens a local Web UI and waits for a browser confirmation, so documentation should explain the default flow and the non-browser option.

Description

  • Added explanatory text and an OpenCode section to both README.md and README-zh-CN.md showing a recommended --no-webbrowser-enhance-prompt configuration example and documenting that the default behavior calls the prompt-enhancer API then opens a local Web UI for user review.

Testing

  • Ran git diff --check which returned no problems.

Codex Task

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 58201b9834

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
Comment on lines +159 to +162
"mcpServers": {
"ace-tool": {
"command": "npx",
"args": [

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Use OpenCode's actual MCP config schema

I checked OpenCode's MCP docs before reviewing this section: local servers must be declared under mcp.<name> with type: "local" and a single command array. This example uses the Claude/Desktop-style mcpServers object plus separate command/args fields instead, so anyone who pastes it into opencode.json will not get ace-tool registered in OpenCode.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2658492137

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +31 to +35
IMPORTANT AFTER THE TOOL RETURNS:
- Treat the returned text as a refined version of the user's instructions.
- You MUST continue fulfilling the user's original request using that enhanced prompt.
- Do NOT stop after displaying or quoting the enhanced prompt.
- Unless the user explicitly asked only for prompt rewriting, proceed with implementation or the next task step.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Exclude error strings from the new “continue after return” rule

The new post-call guidance treats every return value as a usable refined prompt, but EnhancePromptTool::execute() still converts failures into normal text results like Error: ... instead of surfacing an MCP error. If the enhancer API fails, or the browser review is cancelled/times out, an agent that follows this description will continue the task using the error message as its prompt rather than stopping and surfacing the failure to the user.

Useful? React with 👍 / 👎.

Comment thread README-zh-CN.md
Comment on lines +159 to +163
"mcpServers": {
"ace-tool": {
"command": "npx",
"args": [
"ace-tool-rs",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use OpenCode's actual MCP config shape in the Chinese README

I checked OpenCode's MCP docs (https://opencode.ai/docs/mcp-servers): local servers must be declared under mcp.<name> with type: "local" and a single command array. This new example still uses the Claude/Desktop-style mcpServers object plus separate command/args, so readers who paste it into opencode.json will not get ace-tool registered in OpenCode.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 528ad108ec

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +33 to +35
- You MUST continue fulfilling the user's original request using that enhanced prompt.
- Do NOT stop after displaying or quoting the enhanced prompt.
- Unless the user explicitly asked only for prompt rewriting, proceed with implementation or the next task step.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Respect user-requested review checkpoints after prompt enhancement

In MCP clients that follow tool descriptions literally, this new post-call rule can override explicit staging instructions from the user. A request like “enhance this prompt, show it to me, and wait for approval before changing files” is not “only prompt rewriting”, so the current wording tells the agent it MUST continue and Do NOT stop, which can skip the approval checkpoint and start implementation earlier than requested.

Useful? React with 👍 / 👎.

@missdeer
missdeer merged commit bfe18a4 into master Mar 23, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant