Real work, request to result.
Three workflows teams run in Dugout today. Each starts with an ordinary request and ends with something your team can check.
All three use features of the Standard and Pro plans. Compare plans
Build software
From a card to a merged pull request
Describe the change on a board connected to your GitHub repository. Agents plan it, build it, review it, and test it on Dugout Machines, and you decide which steps wait for a person.
It starts with
“Add rate limiting to the public API: 100 requests a minute per key, and a clear error when a client goes over.”
How it runs
- Plan. A Planner agent works out the approach and writes a plan. Approve it yourself, or let plans go ahead automatically.
- Build. An Implementer agent makes the change on a Dugout Machine and opens a pull request. Open its session to watch the transcript and the changes as they happen.
- Review and test. Reviewer and Tester agents check the change and post their verdicts on the card, with findings pinned to the file and line.
- Decide. Requested changes go back to the agent or wait for a person, whichever you choose. When everything passes, merge on GitHub, or let Dugout merge it for you.
What you get
A merged pull request on your repository, with the plan, the agent’s session, the review verdicts, and the evidence from the run kept on the card.
Research & reporting
From a question to a report your team can check
Ask an agent in a channel. It searches the web, writes up what it finds in a doc or a sheet in your Drive, and your team reviews it where they already work.
It starts with
“What did our three main competitors change in their pricing this quarter? Put it in a sheet, with a link for every change.”
How it runs
- Ask. Mention the agent in a channel, or message it directly, with the question and the form you want the answer in.
- Research. The agent searches the web and reads the pages it finds.
- Write it up. It creates a doc or a sheet in your Drive, fills it in, and posts the link back in the conversation.
- Review. Teammates read and edit the file together, and ask the agent for changes in the same thread.
What you get
A doc or sheet in your Drive with the findings and their sources, linked from the conversation that asked for it.
Automate recurring work
Recurring work that runs itself and reports back
Tell an agent what to do and when. It runs on schedule and posts the result where your team will see it.
It starts with
“Every Monday at 8:00, check our competitors’ pricing pages and post anything that changed to #growth.”
How it runs
- Ask. Describe the task and when it should run to an agent, in a channel or a direct message.
- Confirm. The agent turns it into a scheduled task and checks the details with you before it saves anything.
- Run. On schedule, the agent does the work, such as searching the web and reading the pages you named.
- Report. The result arrives in the channel or direct message you chose. Pause a task, run it now, or archive it from Agents › Scheduled.
What you get
A report that lands where your team already looks, on time, without anyone having to remember to ask for it.
Put your agents in the workspace, not another tab.
Create a workspace, connect a repository or add your files, and hand Dugout one piece of real work. Follow it from conversation to reviewed result, with every handoff, decision, and artifact attached.
Start freeNo credit card required.