Define a resource type

This guide creates a new resource type by asking the assistant for it. It assumes a running instance with a model configured (so agents can run) and that you are signed in. For the bigger picture, see Building by chat.

Ask the assistant

Open Chat and describe the type you want in plain language. Name the fields, and call out anything special — an auto-numbered reference, a link to another type, a field that should be normalized:

Create a ticket resource. It has a subject, a status that is either open or closed,
and a customer it belongs to. Auto-number each ticket as TICK-1, TICK-2, and link the
customer to our existing customer type.

The assistant loads its resource-forge and confirms the details it needs — the fields, which one is the human-friendly identifier, and which fields link to other types. Answer its questions, and it builds the type.

What it builds for you

From that description the assistant writes the schema, wires up the extensions, and commits it — no schema for you to write:

• the subject and status fields, with status constrained to open or closed
• an auto-assigned ref (TICK-1, TICK-2, …) via the x-id-strategy extension
• a customerId that links to the customer type, checked on every write

The new ticket table is reconciled immediately — there is no restart.

Verify

Open Resources in the web UI. The ticket type now appears in the list, showing its field count. From here you can work with records.