---
name: dust-call-agent
description: Call a Dust agent to get information (read a slack thread, a notion URL, a google drive document...), perform an action (post a message to slack, create a calendar event, ...), provide context on any topic regarding Dust (the company, current discussions, customers...) or in general have the Dust agent perform a given task.
---

Access Dust agents that have context on all the company, e.g. recent projects, engineering, sales, marketing, etc., via the Dust CLI non-interactively, e.g.:
`$ dust chat -a issueBot -m "create an issue for this: ..."`
`$ dust chat -a deep-dive -m "Research all info we have on kubernetes probe failures in recent weeks."`

A conversation with an agent can be continued after the first message using the argument `-c CONVERSATION_STRING_ID`. The conversation id will be returned in the JSON result from the initial call.
`$ dust chat -a issueBot -c 'TdWyn4aDt1' -m "also add a subsequent issue about this: ..."`

Use `--projectName` or `--projectId` to create the conversation inside a specific project (space). These cannot be used with `-c` (only for new conversations):
`$ dust chat -a prea --projectName "Engineering" -m "summarize recent incidents"`
`$ dust chat -a prea --projectId "abc123" -m "summarize recent incidents"`

Use `-d` / `--details` to get detailed message information in the output (raw event stream, tool actions, and full agent message payload):
`$ dust chat -a prea -d -m "what's the status of project X?"`

If the tool errors because login is needed, ask the user to perform it manually.