Starting a Task

Turn a question or idea into work for your app.

Tasks are where you work with Nuxie. Ask it to find out why fewer users are subscribing, create onboarding for a new audience, or improve an existing paywall. Each Task keeps the conversation and its results together, so you can review the work and keep refining it in one place.

Create a Task

Open For you, choose New Task, and enter your request in the composer. You can start with a question, a problem you’ve noticed, or something you want to make. If your workspace has several apps, include the app you want Nuxie to work on.

Find where new users leave onboarding. Compare the last two weeks with the previous two weeks, then recommend what to change.

For a new Experience, describe what you want users to see and do:

Create onboarding for our running app. Ask about the user’s goal and experience level, then show a plan summary. Include a skip path.

You can attach screenshots, files, and workspace references through Add content. These are useful when you want Nuxie to match your app’s design or work from a particular source. See Giving context and feedback for examples.

If you’re starting from a Report, choose Start Task on the Report. Nuxie receives the finding and its evidence as context.

Continue a Task

Continue in the same Task when you want to change the result. Nuxie can use the existing conversation and work, so you can refine one screen or revisit a finding without starting over.

Keep the layout and images. Replace the second question with weekly availability and use that answer in the summary.

Open a result alongside the conversation to review it. An Experience opens in an editable canvas, while a written result opens as a document. You can move between the results and give feedback in the same conversation.

To interrupt Nuxie, choose Stop in the composer. You can then send different instructions and continue. Work already completed stays in place.

Task results

An investigation gives you an explanation of what Nuxie found, with the data behind it. You can ask follow-up questions or ask Nuxie to prepare a change based on the findings. Sometimes the result is that no change is needed; that conclusion stays with its explanation in the Task.

For a design request, the result is an editable Experience with screens and interactions. You can try it in Preview, make changes yourself, or ask Nuxie to keep working on it.

If Nuxie needs more information, it asks in the conversation. Your answer becomes part of the Task’s context.

Work from another AI assistant

Create and refine paywalls, onboarding, and other in-app Experiences from an assistant that supports remote MCP servers. Add Nuxie with this connection URL:

https://mcp.nuxie.ai/mcp

Choose OAuth authentication, sign in to Nuxie, and approve the account connection. Your assistant can work in the workspaces you can access. For a client that uses an MCP configuration file:

{
  "mcpServers": {
    "nuxie": {
      "type": "http",
      "url": "https://mcp.nuxie.ai/mcp"
    }
  }
}

Ask your assistant to create a paywall or update an existing Experience. When the assistant supports the Nuxie editor, you can preview and refine the screens beside the conversation. Other clients open the work in Nuxie through its Task link. Use that link to resume the same work later.

Publish from Nuxie’s editor to deliver the Experience into your connected app. After integration, new screens and updates reach users remotely without another app release. See Publishing.

Manage or disconnect an assistant from Connected agents.

Proposals

When a change needs approval, Nuxie prepares a Proposal for you to review. It describes what will change and where, such as publishing an updated paywall to a particular app and audience. You can approve it, deny it, or continue the Task with feedback.

A finished design is ready to review; publishing is a separate action. See Reviewing and approving work.