Getting started

A step-by-step first-run guide for using AgentDesk.

Getting started with AgentDesk

This guide walks through the recommended first-run flow for using AgentDesk. By the end, you should understand how to initialize your workspace, introduce yourself, open the dashboard, review the sample task, create an agent, move the task to Ready, wait for completion, open the output, and submit feedback or report an issue.

What you will do

1. Initialize your workspace

   Create your private AgentDesk workspace so your tasks, agents, files, and outputs are isolated from other users.

2. Introduce yourself

   Enter basic information about yourself so AgentDesk and your agents have enough context to support you.

3. Open the dashboard and review Sample Task 000

   Open the dashboard, find the sample task, and review what it asks you to produce.

4. Create an agent

   Create an agent for the sample task. For Task 000, we recommend the FE Dev role.

5. Ask the agent to assign the sample task and move it to Ready

   Chat with the agent and ask them to assign Sample Task 000 to you and move it to Ready.

6. Wait for completion

   Once the task is Ready, it can be picked up for execution. Wait for the agent to finish the task.

7. Open the output and give feedback

   Open Files in your workspace, publish/open the completed Task 000 form output, then submit feedback or report an issue/bug.

Step 1 — Initialize your workspace

When you sign in for the first time, AgentDesk may show that your workspace is not initialized yet.

Click Init Workspace.

Your workspace contains your:

• Dashboard tasks and subtasks.
• Agents.
• Chat history and attachments.
• Artifacts and delivery files.
• Runtime status and activity logs.

Workspace initialization is explicit. AgentDesk should not silently put a normal user into another user’s private workspace.

Step 2 — Introduce yourself

After initialization, AgentDesk may ask you to enter basic information about yourself.

Provide enough context for AgentDesk to understand who you are and what kind of help you need. For example:

Field	Example
Name	Your name or preferred display name.
Role	Founder, product manager, developer, designer, operator, student, etc.
Goal	What you want to use AgentDesk for.
Context	Your project, company, product, or team context.
Preference	How you want agents to communicate or help you.

This information helps agents respond with better context. You can keep it short at first and improve it later.

Step 3 — Open Dashboard and review Sample Task 000

Open the Dashboard.

Find Sample Task 000 and review it before asking an agent to work on it.

Check:

• What the sample task is asking for.
• What output it should produce.
• Whether there are instructions or acceptance criteria.
• Whether the task is still in a draft/inbox state or already ready.

The dashboard is where you will see:

Area	What it is for
Board	Track tasks, statuses, blockers, next actions, and outcomes.
Chat Panel	Talk to the selected agent.
Task Detail	Review task summary, acceptance criteria, notes, activity, runtime events, and linked files.
Workspace Files	Access outputs and files created by tasks.

Step 4 — Create an agent

Open Workspace Management → Agents and create an agent.

For Sample Task 000, we recommend creating an agent with the FE Dev role because the expected output is a frontend-style form/page.

A good first agent should have:

• A clear display name.
• Role: FE Dev for Task 000.
• Enabled status.
• A valid workspace/session mapping.

Step 5 — Ask the agent to assign Sample Task 000 and move it to Ready

Open the Chat Panel, select the FE Dev agent you created, and send a request like:

Please assign Sample Task 000 to me and move it to Ready so it can be picked up for execution.

The agent should update the task so it is assigned correctly and moved to Ready.

When a task is Ready, it means the task is clear enough and allowed to be picked up for execution. Ready does not mean the task is already finished. It means the task can now be selected by the system/agent to start work.

Chat is not the final source of truth. After the agent replies, open the task on the board and verify that the task status is actually Ready.

Step 6 — Wait for the agent to finish the task

Once Sample Task 000 is Ready, the agent/system can pick it up and execute it.

You may see one of these states:

State	Meaning
Ready	The task is clear and can be picked up for execution.
In progress / Active	An agent is working on it.
Waiting	The agent needs your input.
Blocked	The task cannot continue safely.
Done	The task has completed with output or evidence.

Wait until the task reaches Done. If it becomes Waiting or Blocked, open the task and follow the requested next action.

Step 7 — Open Files, publish/open the output link, and submit feedback or issue

After Sample Task 000 is done, open Workspace Management → Files or Delivery Files.

Find the form output created by Task 000.

Then:

1. Open the file or folder for the Task 000 output.
2. Use Public or the equivalent publish/share action if available.
3. Open the generated public link.
4. Review the completed form output in the browser.
5. Submit feedback if the result is good or needs improvement.
6. If something is broken, report an issue/bug for the AgentDesk developer team.

What success looks like

You have completed onboarding when:

• Your workspace is initialized.
• You entered basic self-introduction information.
• You opened the dashboard.
• You reviewed Sample Task 000.
• You created an FE Dev agent.
• You asked the agent to assign Sample Task 000 and move it to Ready.
• You understand that Ready means the task can be picked up for execution.
• The agent completed the task.
• You opened the output from workspace files.
• You submitted feedback or reported an issue/bug.

Next steps

Create and review your first task

Learn how to review a task before execution and verify its output.

Working with agents

Learn how to choose the right agent and keep conversations clear.