Repository navigation
docs: add command line and MCP server guide - #430
Conversation
|
Thanks, this is a well-researched page, and the preset and environment tables match the code. Three small fixes: the stock |
|
Heads up from the check rather than a review: #564 lands the MCP side of the line about "the two Docs are your lane, so I have not touched a word of them. Fold it in whenever is convenient, or |
|
Thanks for the heads-up. I’ll fold those lines in if #564 lands — no
need to touch the branch on my side.
…On Sat, 26 Sep 2026 05:07:32 -0700, Aashish Mahato ***@***.***> wrote:
aashish254 left a comment [(NandhaKishorM/laya#430)](#430 (comment))
Heads up from the check rather than a review: [#564](#564) lands the MCP side of the line about "the two
entry points expose different preset aliases". If that one merges, laya_preset accepts the same
five presets the CLI does -- email joins guard, moderation, triage and model_router -- and
router resolves to model_router, so those two sentences in the tool table collapse into one
list with one long-form name, and the note about the CLI placing text under the preset's state
field becomes true on both surfaces.
Docs are your lane, so I have not touched a word of them. Fold it in whenever is convenient, or
say the word and I will send just those lines as a commit on your branch.
—
Reply to this email directly, [view it on GitHub](#430?email_source=notifications&email_token=CHDJZCY6MDY4HDJ5UTPMCZ35Q6WQJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBUGYYTGNBVGQ2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5846134544), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/CHDJZC2GU7RHD5R7J7FUEH35Q6WQJAVCNFSNUABGKJSXA33TNF2G64TZHMYTGNZVGM4DEMRVGM5US43TOVSTWNJVG4ZTCMJZHA2TDILWAI).
You are receiving this because you authored the thread.
|
5060d3a to
becd5e4
Compare
Rebases onto current main and re-verifies the page against the code it describes, then fixes four statements that current main no longer supports. The rebase needed care. The previous head was a merge commit, and the maintainer's requested corrections lived in that merge's hand-resolved conflict resolution rather than in an ordinary commit. A plain rebase drops merges, so replaying the branch produced a page that silently lost all three of them. The guide is restored with those corrections intact, plus the `laya_shortlist` and `laya eval` sections. Corrected against the code: * `laya_predict_batch`, `laya_route_batch` and `laya_decide` are registered by the MCP server but were missing from the "Available tools" table, which listed five of the eight tools. The 0.3.21 sweep put batching and the token budget on every surface; this page still described the pre-batch set. * `LAYA_AUTO_TASK` is read by the MCP server (`auto_task_detection=`) and documented in its module docstring, but was absent from the environment table. * The preset paragraph claimed the two entry points expose different preset aliases. They no longer do: `laya_preset` now carries all five presets the CLI has, with `router` accepted as an alias for the canonical `model_router`, and it performs the same state-field placement. The paragraph now states the shared list once and notes the alias, instead of describing a difference that no longer exists. Verified still true, and left as written: the stock `laya-mcp-server` launcher builds its Router without installing hooks (there is no hook reference anywhere in `laya/mcp/server.py`), `laya.hooks.set_default_hooks` is the documented way to install them, `noul` is the probability of true, an empty line ends interactive mode, `DEFAULT_SHORTLIST_K` is 20 with mean-pooled embeddings from the answering checkpoint's own encoder, the transport is stdio only, and the three README anchors this page links to still exist. `docs/index.md`'s closing sentence now lists only routing, the HTTP API and confidence gating, as requested, with the guide's own table row carrying the command line and MCP server. Checks: `tests/test_doc_tables.py` 109 passed, `tests/test_packaging.py` 106 passed. All five relative links in the guide resolve. The docs workflow's `zensical build --strict` gate was not run locally — zensical is not installed in this environment.
|
Rebased onto current main, and the three fixes are in: hooks now say the stock launcher installs none,
Verifying the rest of the page against the code turned up three more things the 0.3.21 sweep invalidated:
Still true and left as written: the stock launcher builds its Router with no hooks anywhere in One thing that is not mine: |
|
Passed checks and merged. Thank you @Bruce-Yii! It ships in 0.3.22. |
What
docs/cli-mcp.md, a task-oriented guide for choosing and using the locallayaCLI versus the built-in MCP stdio server.docs/index.mdand remove the index's stale claim that CLI/MCP material is README-only..nav.ymlchanges.Why
YU-86 covers the standalone Command line and MCP server item in #390. The README has short summaries, but readers need one page that explains the interface boundary, source-backed commands/tools, first-use model loading, MCP client configuration, environment variables, and the structured-decision/action boundary.
This intentionally does not duplicate the adjacent Routing (#416) or Questions and answers (#418) guides, and does not absorb the still-coordinated HTTP API surface.
Source verification
970dc8c5f63d7b886a68409493f37d569424f933(main, confirmed through the GitHub branch API).64dbf55617c70d7556bed5ee81eff04403567c70.pyproject.tomlentry points,laya/cli.py,laya/mcp/server.py,laya/mcp/tools.py,laya/mcp/__init__.py, and the existing CLI/MCP tests.main:laya_status,laya_route,laya_predict, andlaya_preset.laya_shortlistMCP extension), docs: add the Routing guide (#390) #416, and docs: add the Questions and answers guide (#390) #418.How it was verified
Checklist
mainRefs #390