BotchiDocs
Dashboard

Create an agent

Create a specialist, decide who can use it and give it the resources it needs.

On this page
View as Markdown

Create an agent for one clear job. Define its authority before giving it tools or company files.

Before you begin

You need a business account and owner or dashboard editor access. Create team roles if you want members to use the agent.

Create the specialist

  1. Open Agents and choose New agent.
  2. Enter Name and Domain. Use a domain that identifies its business area, such as Sales.
  3. Write Identity: its role, responsibilities, forbidden actions, tone and when it must ask a person. Identity is required; detailed procedures belong in skills.
  4. Choose the team roles under Role access.
  5. Choose Only its own folder, the default, or Whole Workspace. Whole Workspace gives read and write access to shared files, subject to system protections.
  6. Select Create agent.
  7. Open Instructions and add a first skill for the recurring task you want it to handle.
  8. Open Connections and attach the tools and specific folders it needs.
  9. Try a representative task in Chat.
  10. Save the completed exchange as an eval case.

The agent uses its identity in every run, and loads relevant skills when needed. Its tools and file access constrain what it can do.

  1. 01Name, domain, identity, role accessNew agent
  2. 02Identity in place, then its first skillInstructions
  3. 03Attach tools, presets, panelsConnections
  4. 04Continue your conversation with the agentChat
  5. 05Turn a good run into a regression caseEvals
The whole path, end to end.

Botchi generates the member-facing description from the identity, in the same language. Review role access before inviting your team to use the agent.

Watch out — New agents start with Web connected. Detach it from Connections if the agent should not use those public-web tools. Code Executor can also access the internet during ordinary runs.

Start from existing work

Choose Duplicate existing agent from the New agent menu to reuse identity, tools, presets, role access and Workspace access. Memory, run history and chat channels stay with the original. Review inherited permissions before use.

Choose Community templates to start from a community brief. Use template sends it to the dashboard Assistant for adaptation to your tools and rules. Review its proposal and approve creation. Templates grant no capabilities by themselves.

Related