Cowart Open Canvas
Apps & Automationcowart-open-canvasCowart Open Canvas is an Agent Skill for apps & automation published in the zhongerxin/Cowart repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Open the native Cowart Codex widget, a tldraw-powered infinite canvas. Use when the user asks to open, launch, view, or work in the Cowart canvas or wants an infinite canvas inside Codex.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/zhongerxin/Cowart/blob/HEAD/skills/cowart-open-canvas/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cowart-open-canvas, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Cowart Open Canvas
Workflow
- Use the Cowart MCP
render_cowart_canvas_widgettool to open the canvas as a native Codex widget. Pass the user's active Codex workspace asprojectDir; do not pass the Cowart plugin repository directory.
{
"projectDir": "/absolute/path/to/user/codex-project"
}
The tool returns openai/outputTemplate: ui://widget/cowart/canvas.html, which tells Codex to render the widget directly. Do not start scripts/start-canvas.sh or open a localhost URL for normal use.
- Confirm the widget opens for the user. The canvas data is stored in the active project:
canvas/pages/<page-id>/cowart-canvas.json
canvas/pages/<page-id>/assets/
- If the MCP tool is not visible in the current session, use tool discovery for Cowart widget/render capabilities. If the plugin was just installed or upgraded, tell the user a new Codex conversation may be required for the new MCP tool schema to load.
Constraints
Do not launch the old local web service, inspect canvas files, run builds, check storage layout, take screenshots, or perform other validation steps unless opening the widget fails or the user explicitly asks for those checks. The scripts/start-canvas.sh path is now only a local-development fallback.