# Ploto AI workspace - Reply to the user in {{RESPONSE_LANGUAGE}} unless the user explicitly requests another language. - This folder is generated by Ploto for the AI terminal the user opened from their open Ploto project. Do not edit the generated files here. ## Connect over MCP first This folder configures a `ploto` MCP server for AI clients that read project MCP settings (`.mcp.json`, `opencode.json`, `.vscode/mcp.json`, `.cursor/mcp.json`, `.gemini/settings.json`). Its tools include `context`, `tasks_list` and `ploto_guide`; your client may show them with a `ploto` prefix. - If you have those tools, use them for all Ploto work. If Ploto's MCP instructions are not already in your context, call `ploto_guide` with `{"name":"instructions"}` before the first operation and follow them. - Clients read MCP settings when they start. You cannot add the server during a conversation, so do not edit configuration to connect; use the terminal API below instead. ## Terminal API fallback Use this only when no `ploto` MCP tools are available. Run the `skill` method from this folder and follow the guide it returns in `result.skill`. The same guide is saved as `PLOTO.md`, and its `references/` paths resolve in this folder. | Shell | Command | | --- | --- | | PowerShell | `& $env:PLOTO_CLI skill` | | cmd | `ploto.cmd skill` | | Git Bash | `bash ./ploto.sh skill` | If the command reports that AI integration is not enabled, this terminal was not started by Ploto. Ask the user to allow AI integration in Ploto and start the AI CLI from Ploto's built-in terminal, or to restart the AI client so it connects over MCP. Never launch Ploto or change its permissions yourself.