move_project

Move a project inside its section and group of your sidebar (pinned, your projects, or public ones): after or before another project there, or to the top or bottom. At most one of after, before, to; with none (and no group) it goes to the top. group files it in one of your own groups (save_project_group makes them), null or "" takes it out. A pinned project keeps its group and shows in it too: after/before/to move it among your pins; in "group" places it inside its current group instead (no re-filing).

• 2026-10-06 — New optional group argument: a group name or id files the project in one of your sidebar groups, null or an empty string takes it out of its group (create groups with save_project_group). Without after, before and to, a call with group only files the project and no longer moves it to the top; after and before must name projects of the same group. Filing and placing are one step: when the position is refused the project is not filed either.
• 2026-10-07 — A pinned project also shows inside its group now: after and before may name its pinned group members. New optional in: "group" places a pinned project among the projects of its current group (needs after, before or to; the project is not re-filed and its pin order stays; an anchor outside the group is refused). Without it a pinned project moves among your pins as before; with group a pinned project is re-filed and placed inside that group, but group null with a place is refused for a pinned project. list_projects with group lists them in the group order.
• 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
• 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.