← Planner5D: Plan, Build, CreateCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Planner5D: Plan, Build, Create
Snapshot Oct 9, 2026 · 18:02 UTC · version 1.3.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use the Planner 5D app in ChatGPT or Codex for native projects, spaces, design, recognition, furnishing, model imports, furniture fit, AI Studio images/videos, specifications, quotes, project documents and exports. Route a task to its native workspace and tools before editing.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 383
},
{
"relative_path": "references/ai-studio.md",
"size_in_bytes": 2934
},
{
"relative_path": "references/workspace.md",
"size_in_bytes": 2956
}
],
"name": "planner5d-native-app",
"skill_md_contents": "---\nname: planner5d-native-app\ndescription: Use the Planner 5D app in ChatGPT or Codex for native projects, spaces, design, recognition, furnishing, model imports, furniture fit, AI Studio images/videos, specifications, quotes, project documents and exports. Route a task to its native workspace and tools before editing.\n---\n\n# Planner 5D native app\n\nComplete the requested work in the connected Planner 5D account through these server MCP tools:\n\n1. Reuse the selected Planner 5D app or the panel already associated with this chat. If app context supplies a public `panel_id`, begin with that ID; do not call the opener merely because this is the first question. Call `open_planner5d` only when no Planner panel is selected or open, or the user requests a new one. Retain the panel ID for follow-up work.\n2. Call `get_planner5d_tools` with that ID. A ready response provides `document_id` and the active native tool index. For actual input schemas, request one to eight `tool_names`.\n3. Execute native reads with `read_planner5d`; execute navigation and changes with `change_planner5d`. Both accept `panel_id` and an `invocation` containing `operation_id`, `document_id`, `tool_name`, and `arguments`. The arguments must match that native tool's live schema.\n4. Give each logical call a unique `operation_id`; reuse the exact ID and input to recover an uncertain response. Never create another ID just to replay an unconfirmed mutation.\n5. Refresh discovery after navigation. Do not use the old document ID for the destination page. If discovery is still `connecting`, allow the selected panel to finish loading and retry discovery. If a visible selected panel is reported `closed`, refresh its app context or use its in-place reconnect control when available. Report a connection failure if recovery is unavailable; do not silently open a replacement window or switch to an unrelated browser tab.\n\nRead `getWebMcpGuide` once through `read_planner5d`, then request the needed tool descriptions and schemas. The browser executes the original native operations; the MCP server transports requests and receipts. Do not call app-only delivery or session-renewal helpers, inspect private launch metadata, or substitute private application APIs.\n\n## Choose the workspace\n\n- Keep navigation available in the app: `goToSpaces`, `goToEditor`, `goToEditorProject`, and `goToPurchase` expose their native destinations. A navigation result schedules a page change; refresh capabilities and confirm the destination before dependent work.\n- For a new home, design the shell and room access graph, create an editable project with `projectCreateScene`, and open its returned project hash. `goToEditor` followed by `editorCreateScene` is the native editor alternative. Existing projects start with their identity, revision and permissions from `editorGetContext`.\n- Editor geometry tools become available after an editor is loaded. Spaces, documents, models, AI Studio and collaboration have their own mounted native providers. Navigate to the required provider rather than concluding the entire product lacks the capability.\n- Native account, ownership, subscription and credit checks still apply. A denied action is not a reason to call a private application API or use another account.\n\n## Use the relevant instructions\n\n- Home and room design, catalog/furnishing, kitchens, measured fit, materials and reference-photo reconstruction: use `planner5d-webmcp` and its relevant references.\n- The person's furniture from a product photo/link or 3D file, owned-model reuse, measured fit and showing that product in an interior: use `planner5d-model-import`.\n- Image/PDF/CAD plan recognition and measured source comparison: use `planner5d-floorplan-recheck`.\n- Photorealistic screenshot-based image generation: use `planner5d-ai-render`.\n- Space/project organization, documents, imports, sharing, comments, quotes/specifications and native CAD/PDF exports: read [workspace operations](references/workspace.md) and discover the live provider.\n- Image/video creation, reference edits and visual content in a Planner AI Studio sheet, including work beyond home design: read [AI Studio](references/ai-studio.md). Scene-based photoreal images use `planner5d-ai-render`.\n\nUse the host's normal file and external-information tools for user-requested supporting research or arithmetic. Geometry, object placement, native history and project saving remain Planner operations. Copilot chat IDs, DPL, Modal design runtimes and private renderer state are not extension interfaces.\n\nFor a combined request, carry the result between workflows: imported/recognized plan → source comparison → requested furniture/model placement and fit → composed native scene → AI render. A request to show a product in the person's interior includes the final scene-based image when requested; do not stop at an uploaded model or imported empty plan.\n\n## Finish the actual request\n\nFor a requested Planner design, create and verify an editable native project. A standalone concept PDF or generated picture is not a substitute for that project. Supplementary files are appropriate when requested or exported from the verified native result.\n\nKeep stable operation IDs, inspect partial outcomes, and recover uncertain writes before retrying. Verify the requested rooms, connections, dimensions and outputs, then return the actual project and accessible native artifacts. Do not claim an accepted job is a completed render, imported model or downloaded drawing.\n"
}SHA-256 of public snapshot: 431a0045c05a46aa764e2bb0e5c1ac335303a0904f57d7672a7c2e4537533539