Follow-up to #107: /v1/coding_plan/search API needs pagination support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- api, backend-api-design
Research direction
Start with MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py and inspect the web_search tool, then trace the underlying API gateway that proxies /v1/coding_plan/search. Confirm where pagination parameters and response behavior can be implemented. Done means the API accepts a documented count and page or offset mechanism, after which the CLI and SDK can expose matching options.
Written by the indexing model from the issue text.
Description
Follow-up to #107
Issue #107 (closed by docs-only PR) asked for pagination on mmx search query because the API returns at most 10 results per call.
Investigation result
The /v1/coding_plan/search endpoint does not currently expose any pagination parameter. The canonical reference client (MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py, web_search) only sends {"q": query} and the response is just { organic: [...], related_searches: [...] } — no count, page, limit, or offset is accepted or returned.
In other words, the 10-result cap is a hard limit imposed by the API, not by the CLI. The CLI cannot expose pagination flags that the server will not honor.
What is needed on the API side
To make #107 actionable, the /v1/coding_plan/search endpoint needs to accept a pagination mechanism. The simplest options would be:
- Add a
countparameter (1–N, default 10) so callers can request larger pages, and - Add an
offsetorpageparameter (1-indexed or 0-indexed) so callers can paginate beyond the first page.
Both should be added to:
MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py(web_searchtool)- Any underlying API gateway that proxies the request
Once the API supports these, the CLI can be updated to expose --page and --limit flags (and the SDK's SearchSDK.query can accept the same options).
Tracking
Closing the docs gap for #107 in this repo was done in the matching PR. This issue tracks the API-side work.
Refs #107.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 181
- Avg merge
- 9h 4m
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MiniMax-AI/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
MiniMax-AI/cli#259 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MiniMax-AI/cli#258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
MiniMax-AI/cli#265 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
MiniMax-AI/cli#260 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
MiniMax-AI/cli#257 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·