Author automations with an AI assistant

Connect your assistant through MCP before asking it to prepare work in Titan.

Check your permissionsCopy Anchor Link

Using an available strategy and authoring its source are different permissions. An account can have access to run a strategy without permission to edit strategy definitions, prompt content, or tool sets.

If Titan reports that strategy authoring is disabled, ask your Titan administrator to enable the required authoring permission. The assistant cannot grant that permission to itself.

Describe a concrete workflowCopy Anchor Link

Tell the assistant:

• The task and the app or device it should operate.
• What a successful result looks like.
• The inputs that change between runs.
• The actions that require your decision.
• When to stop or report a failure.

For example:

Create a strategy for this workflow using the tools available in my Titan account. First inspect existing reusable strategies and prompt content. Identify the required account, text, and media inputs. Show me the proposed steps, completion condition, and stopping conditions before saving the definition.

Review, save, and releaseCopy Anchor Link

Have the assistant identify the exact strategy it is editing, read its current version, and save the reviewed definition. Ask it to read the saved version back before creating an explicit release.

If another edit happened in the meantime, resolve that change before saving again. If a save or release response is uncertain, have the assistant read the current state rather than repeat the write blindly.

A release records fixed versions of its dependencies. Updating a prompt or a called strategy later does not silently update an earlier release.

Prepare a reusable run setupCopy Anchor Link

A run setup records your execution choices. Ask the assistant to read the strategy's current requirements, choose your device and adapter, and select your own resource rows and manual inputs.

Save a reusable setup for this exact strategy release. Show the device, AI adapter, resource selections, and manual inputs. Read the saved setup back and give me its ID and version. Do not start it yet.

Using someone else's shared strategy does not give you their saved setup, account data, or private source. Provide your own execution inputs.

Try a small executionCopy Anchor Link

Run one item on one phone, inspect My Runs, and check the resulting phone state. Expand to a queue after the initial result is satisfactory.

Authoring and release preparation happen through MCP. Use the browser's strategy review and monitoring pages to inspect the resulting work.