Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rundock.ai/llms.txt

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

When you open Rundock for the first time, a guided sequence walks you through choosing a workspace and creating your first agent. This page sets expectations for what you will see and what each step is for. Nothing you do here is permanent. Workspaces, agents, and settings can all be changed later. The goal of first-run is a working team you can talk to, not a perfect one.

​
What you will see

​
1. Doc opens the conversation

Rundock launches and the conversation panel opens with a single agent already talking: Doc. Doc is Rundock’s built-in guide. It is a platform agent, not a specialist you build, and it is there to walk you through the first-run flow. Doc is part of Rundock and lives outside your workspace. You do not need to create or configure it. It is always available, and it stays out of the org chart with your own agents.

​
2. Doc asks for a workspace folder

Doc asks you to pick or create a workspace folder. A workspace is a folder on your machine that holds everything Rundock uses for one team: the agent files, the skill files, and any shared knowledge documents. The full concept is covered on the Workspaces page. You have two options:
  • Pick an existing folder. Use this if you already have a folder you want Rundock to manage, or if you are joining a team that has shared a synced workspace folder with you (see the team workspace setup guide for that case).
  • Create a new folder. Doc will create the folder structure and place the initial files in it.
For a first run, pick a memorable location like ~/Documents/Rundock-Workspace. You can move it later if you change your mind.

​
3. Doc walks through first-agent creation

Once a workspace is selected, Doc helps you create your first agent. It will ask for:
  • A name. Short and memorable. The name is used in conversation (“ask Penn to draft a post”) and on the org chart card.
  • A role. A short description of what this agent is responsible for. Two to four words is typical.
  • Instructions. What this agent does, what it should not do, and any voice or tone guidance. Doc will offer a starter template you can adjust.
Doc saves the agent as a markdown file in your workspace. You can edit the file later in any text editor or through Rundock’s interface.

​
4. The org chart appears

Once the first agent is saved, Rundock renders the org chart with that agent visible. You can talk to the agent directly, or you can talk to the orchestrator and it will route work to the right specialist. Right now, with one specialist, both routes go to the same place. This is the working state. From here you can create more agents, write skills, set up routines, or just start using the agent you have.

​
Where to next

Two paths from here. Pick the one that matches what you are doing.

Quick start

Give your first agent a real task and get a useful result back in under ten minutes.

Set up a team workspace

Share your workspace across a team using Dropbox, OneDrive, Google Drive, or git.