Skip to content
Workflow

Build a custom AI coding workspace

Turn a recurring task into a board or panel you can use directly: a release checklist, a ticket desk or a notebook linked to agent work.

The path through the task
  1. Describe the workspace
  2. Build a Morph
  3. Use and refine it

Before you start

  • The Empryo desktop app and a project to hold the Morph. Morphs are currently marked experimental.
  • A small workflow with clear inputs and actions.
  • Approval for any agent instructions or tools the Morph adds.

Work through it

  1. Name the job and the controls

    Decide what you want to read, edit and launch. A release board might need a version field, checkboxes and a button that prepares a review prompt.

    Check: Separate direct UI actions from actions that genuinely need an agent.

  2. Choose where it lives

    Ask the agent to create one Morph JSON file. Start with a panel or dock; choose a full canvas when the board should occupy the workspace. Add composer or chat-frame styling only when it helps the task.

    Check: Review the file and approve its agent layer if it adds rules, skills or tools. UI-only changes do not imply that approval.

  3. Try the controls before relying on them

    Change a field, reorder a row and inspect the prepared prompt. Check any API action and its confirmation behavior. Refine the Morph as you would another project file.

    Check: Switch back to chat and verify that your existing conversations remain available.

Choose the working surface

Panel or sidebar

Keep a checklist or reference next to the conversation.

Composer dock or extension

Put a task control at the place you use it.

Full-workspace canvas

Work from a board or custom view; the chat moves aside and agents can continue behind it.

A prompt to adapt

Replace the task details with your own. This is a suggested instruction, not a recorded result or a security policy.

Suggested prompt
Build a release-checklist Morph for this project. Include a version field, editable checks and a button that prepares a review prompt without sending it. Start as a side panel. Do not publish a release or call external APIs.

Keep these boundaries clear

Open the detailed guides

Checked against the documentation on .