Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.agentdesk.team/llms.txt

Use this file to discover all available pages before exploring further.

​
Dashboard Board

The board is the main place to understand work state. It is stronger than chat history for determining whether work is waiting, active, blocked, or done.

​
What a task should show

A useful task usually includes:
  • Title.
  • Status.
  • Owner or executor.
  • Priority.
  • Summary or source request.
  • Acceptance criteria.
  • Next action.
  • Latest update.
  • Attachments, artifacts, or delivery links.

​
Activity vs Runtime

TabMeaning
ActivityHuman-visible updates, edits, notes, status changes, and review comments.
RuntimeSystem/orchestration events, dispatches, active assignment updates, and automation details.
Keeping these separate helps users understand what happened without mixing product updates with internal runtime noise.

​
Notes

Task notes can include safe Markdown. Avoid pasting secrets into notes.

​
Evidence

Before accepting a task as done, look for the right proof:
  • Screenshot or browser proof for UI work.
  • Test output for code/API changes.
  • Delivery file for user-facing documents or assets.
  • Runtime/log evidence for orchestration behavior.
  • Clear blocker note if work cannot proceed.