Invite a guest chef from Studio · Level 2

This lesson has no code. You build a second agent in the browser and give it the same kind of job as the specialist chef, so you can see what an app-defined agent gives you that a Studio agent cannot.

Step 1: Pick a handed-off dish

Open the Tom yum soup ticket from lesson 5, or any ticket labelled assign-to-agent with the Agent task triggered comment. Keep its key at hand.

Stuck? Moving a ticket to “Approved for Agent” does nothing

Done: a ticket with assign-to-agent and the Agent task triggered comment is open

Step 2: Create an agent in Studio

Atlassian’s own products · House systems

Studio agent · a guest chef

Rovo Studio builds agents in the browser: instructions, knowledge and built-in tools, with no app and no code. A Studio agent is quick to make and easy to change, but it can only use what Studio offers. It has no access to your app’s functions, your supplier key or your egress list.

In the kitchen A guest chef brings their own knives but has no supplier accounts and no keys.

Open Rovo Chat, open the agent menu at the top, and choose Create agent. Studio opens.
Choose to start from blank.
Name it Menu researcher - your name, so it does not clash with anyone else’s on a shared site.

Stuck? The specialist chef does not appear in Rovo

Done: a draft agent called Menu researcher with your name is open in Studio

Step 3: Write its instructions

Paste these instructions, or write your own with the same limits:

CodeInstructions

You research dish tickets for a restaurant kitchen that plans its work in Jira.
Work only on the ticket you are given. Read it first, including its comments.
Write one comment with: what the dish needs, what to source, and any risks.
Mark anything you could not check as unchecked. Never invent a supplier or a source.
Never change the ticket's status, assignee or summary, and never create new tickets.

The last three lines are the limits: say what is unchecked, invent nothing, and change nothing but the comment.

Done: the instructions are saved and include the three limits

Step 4: Give it Jira, and only Jira

In the agent’s tools or skills, turn on reading Jira work items and adding comments. Where Studio lets you limit them to a space, choose Kitchen. Leave everything else off, then publish the agent.

Stuck? The specialist chef does not appear in Rovo

Done: the agent can read work items and add comments, and nothing more

Step 5: Let it work the ticket

On the ticket, start the agent from its Agents area, for example with Start work, and choose your Menu researcher. Assigning the ticket to an agent only changes who owns it; starting it is what makes it work.

When it finishes, reload the ticket and read its comment.

Stuck? The specialist chef does not appear in Rovo

Done: the ticket has a research comment from your Studio agent

Step 6: Compare the two chefs

Ask both agents about the same ticket: the specialist chef in Rovo Chat, the Menu researcher on the ticket.

The specialist chef calls your app’s actions: it can use the supplier with your key, and publish notes once per ticket because your code remembers.
The guest chef from Studio works only with Studio’s tools: quick to change and no code, but no supplier account, and nothing that remembers what it already published.

Use Studio for agents that read and write what Atlassian already offers. Build one into a Forge app when it needs your code, your data or an outside service.

Done: you can say one thing each agent can do that the other cannot

What you built

The same app from Level 1 now runs a back kitchen: a page in Jira where the head chef drops meeting notes, a queue and a consumer that answer at once and work afterwards, Forge LLM to split the notes into dish tickets, a Confluence menu of record, a handoff at the pass and a Rovo agent of your own. Every piece reuses something from before: the recipe card shows on every ticket the sous-chef writes, and the specialist calls the same supplier.

The optional last lesson adds a delivery door, for other systems to send menus.

Check what you know

Eight questions on Level 2. Each answer explains itself.

Question 1 of 8
From lesson 2, why does the desk answer before any ticket exists?
Question 2 of 8
Who is the reporter of a ticket the prep cook writes?
Question 3 of 8
What goes on the menu-jobs queue?
Question 4 of 8
Why does acceptMenu save the menu before it pushes the slip?
Question 5 of 8
In lesson 3, who decides which dish tickets get written?
Question 6 of 8
The prep cook crashes after two tickets and Forge runs the slip again. With checkpoints, what happens?
Question 7 of 8
Why does the handoff read the ticket’s labels from Jira instead of from the event?
Question 8 of 8
What can the specialist chef do that the Studio agent from lesson 7 cannot?