Get started with Prism

A successful first run means more than receiving a chat answer. Build a small tool, use it, reload the page and check that its data remains.

1. Set your profile and timezone

Open Settings → Profile, set a display name and an IANA timezone, or use the browser timezone. This gives the agent the right local time for requests and new scheduled jobs.

2. Create a workspace for one purpose

Create a workspace named Reading list. A dashboard workspace groups a conversation and widgets; the execution workspace is the container where code and data live. Tell the agent what information matters and what actions you need.

3. Ask for a small usable tool

Build a reading-list widget in this workspace. Let me add a title and URL, mark an item as read, and remove it. Persist the list using a custom backend tool and a data file in the workspace. Use the Prism theme.

Watch the tool calls and use Approval → manual if you want to review each action. The agent can combine code execution, files, tools and widgets. A separate container is useful for an actual service, but is not required for a simple persistent list.

4. Verify the result

  • Add two items, mark one read and reload the page. Check the list still exists.
  • Ask for a filter or search field; check the existing data survives the change.
  • Open Settings → Resources to inspect backend dependencies before deleting a widget or workspace. Review shared resources and retained data.

5. Add knowledge when it is useful

Configure an embedding model before indexing documents. Add a small document in Knowledge, describe the collection’s purpose, then ask a question whose answer is in it. Check the retrieved sources. A chat model does not automatically provide embeddings.

6. Expand one capability at a time

Connect mail or a calendar only when needed. Try an automation after checking its timezone and expected output. A running task can continue when you close the browser; return to the same conversation to see its result. Stop cancels it; a server restart interrupts it.

Understand widgets, tools and resource lifecycles →