Give direction.
Keep creative control.

An agent uses carvercat’s supported operations through local MCP. It can discover state, author and revise a composition; you can inspect and edit the same project in the visible editor. AI is an optional route, not a requirement for drawing or animation.

1. Open the editor and a disposable learning project yourself.
2. Follow the exact client/setup instructions for the qualified package. Do not paste internal Dev paths into customer configuration.
3. Ask the agent to discover available operations and identify the open comp.
4. Confirm the target and current state before the first edit.

A client reporting a connection is not proof that the editor is ready or the intended document is open.

In the open test comp, create a lower third reading Alex Morgan / Independent creative. Use a simple shape and a short entrance. Keep text and colour editable. Show me the result and stop before exporting or sending it.

Name the intended outcome, preserve requirements and stopping point. Discovery should supply supported operations; the agent should not invent a tool name or bypass a refusal.

• Confirm the intended objects and comp changed.
• Inspect a rendered/visible frame, not only command success.
• Scrub the entrance and settled pose.
• Check text, geometry, timing and save/reopen where applicable.
• Ask for a summary of what changed and what remains uncertain.

Ask the agent to stop. Change the wording yourself. Before its next edit, require a fresh state read so the agent works from your current project instead of overwriting the change with stale assumptions.

For a timing revision, ask it to adjust only the entrance and preserve the manually changed wording. Concurrent activity is not a guarantee of conflict-free collaboration.

After a disconnect or timeout, inspect document state, history or output before repeating the operation. Reconnect and read state first. For external delivery, inspect the actual destination; blindly replaying a send can duplicate work.