* feat(operations): add create_project operation across agent, mcp, and cli
* fix(api): remove legacy team creation endpoint
* fix(api): preserve ProjectInfo response on POST /teams/:teamId/projects
* feat(cli): add standalone downloads and installers
* fix(cli): silence PowerShell download progress
* fix(cli): use framework APIs for Windows verification
* fix(cli): preserve null backup path during Windows updates
* docs(cli): translate native installation quickstart into Chinese
* feat(operations): move MCP to /mcp and add search, comment, metadata, version, and upload operations
- Serve the MCP server at /mcp instead of /api/mcp
- Add search_assets, copy_assets, get_folder_instructions, list_comments,
create_comment, resolve_comment, list_metadata_fields,
update_asset_metadata, create_version_stack, list_versions, and
remove_version on the agent, MCP, and CLI
- Add create_file and create_version (agent, MCP) with Creation Context
metadata, and complete_upload (MCP) for presigned two-step uploads
- Replace the native agent create_file/create_version tools with
Operation-backed ones
- Route the comment-complete, metadata, copy, version stack, and
AGENTS.md read REST endpoints through their Operations
* docs(readme): add built-in MCP server and CLI to features list
* feat(asset-read): expose read_asset on MCP and the CLI
Enable the mcp and cli surfaces for read_asset and get_asset_render.
- MCP: add per-Operation tool extensions. The read presenter attaches up
to 8 images (2 MB each) inline, lists image links, supports
inlineImages: false, and tells the model to call get_asset_render when
a render is pending. Storage keys are stripped from the result.
- CLI: generated commands can flatten object inputs into prefixed flags
(cli.flatten) and omit fields (cli.omit); add per-command extensions.
New `read` and `render` commands print image links, download them with
--out, and support --no-wait with a printed `render <taskId>` hint.
- Round frame timestamps in labels to 3 decimals.
* fix(mcp): make tool input schemas portable to single-type dialects
Nullable inputs were emitted as `type: ["number", "null"]` (or a `null`
anyOf branch), which clients that map tool schemas onto an OpenAPI-style
subset (e.g. Gemini function declarations) may reject.
- Make read_asset's startPage, endPage, and degree optional instead of
nullable.
- Move null handling into a shared dropNullOptionals helper in
@shumai/operations that also strips nulls inside nested config
objects. The agent uses it, and the MCP server applies it before the
SDK validates arguments, so models that send null keep working.
- Test that no Operation input schema (and no listed MCP tool) uses a
nullable type.
* feat(asset-download): share download_asset across agent, MCP and CLI
Turn the agent-only download_asset tool into an Operation on all three
surfaces.
- download_asset takes up to 50 file or version stack IDs and returns
presigned links. proxy (default true) picks the web preview when there
is one, as the agent always did; proxy: false returns the original.
Folders are rejected. Read is checked on every ID before anything runs.
- Agent: an extension saves the files into the .pi sandbox and keeps the
agent-only storage key mode (e.g. frames from read_asset). Agent tool
extensions gain description, parameterOverrides and intercept.
- CLI: `shumai-cli download <assetId...> [--out <dir>] [--original]`
streams files to disk without overwriting existing names.
- read_asset's unsupported-type error now names the right way to
download on each surface (download_asset, or `shumai-cli download`).
- Add the Download Asset toggle to agent settings.
Rebuild the CLI on commander. Commands for every cli-surface Operation
(project ls, ls, mkdir, rename, move/mv, delete/rm) are generated from
@shumai/operations: positionals, options, choices, numeric parsing and
help text come from the Zod input schema. They call POST /api/ops/:name
with x-shumai-client: cli.
Existing invocations keep working. Adds --json, ls --type/--first/
--after, typo suggestions, and generated help. upload and create-version
stay hand-written. Drops the unused @shumai/core dependency.
New tokens are 32 random bytes with a shumai_ prefix and are returned
only once at creation. The list endpoint returns a 4-character hint
instead of the plaintext. A migration hashes existing tokens in place so
they keep authenticating.