> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/digital-worker-mode.md).
# Digital Worker Mode
Learn what Digital Worker Mode is and how a Digibee Digital Worker builds, deploys, and monitors your integrations from a specification you review and approve at each step.
## **What it does**
Digital Worker Mode lets you delegate the integration lifecycle to a Digibee Digital Worker: an AI specialized in enterprise integration, not a general-purpose coding assistant. You describe your goal in natural language, and the digital worker handles discovery, build, deployment, and monitoring, working from a specification that you review and approve at each step.
## **How it works**
Digital Worker Mode follows a structured cycle, not a single one-shot generation.
{% stepper %}
{% step %}
### **Provide a goal**
Instead of step-by-step instructions, you give the digital worker an objective. Digital workers aren't interns: like a consultant, they run independent discovery, apply known integration patterns, and come back to confirm your preferences and trade-off decisions.
{% endstep %}
{% step %}
### **Co-create the spec**
Together, you produce a specification made up of a business-facing project brief and comprehensive technical documentation. Every integration gets one authoritative document instead of scattered tickets, chat threads, or knowledge trapped with whoever built it. This document records every requirement, data mapping, and decision, and stays up to date as the integration evolves. It doubles as your control surface for alignment and governance, and as the reference anyone can pick up later.
{% endstep %}
{% step %}
### **Build and review**
The digital worker builds the integration to spec. It reuses enterprise application connectors along with hardened building blocks for logic, data transformation, and validation. Then it tests the integration and sends it back for your review. Nothing deploys without your approval.
{% endstep %}
{% endstepper %}
## **When to use it**
Digital Worker Mode is the fastest way to build on Digibee, and the recommended approach for most integration work. Instead of choosing between modes case by case, use it by default: describe your goal, review the spec the digital worker proposes, and approve the build.
You keep full control the whole way. Every requirement lives in the spec, every change to it needs your sign-off, and nothing deploys without your approval. What changes is where your time goes: less of it spent building step by step, more of it spent reviewing, directing, and refining the spec that defines the integration.
## **Next steps**
Ready to try it? Click **Digital Worker Mode** in the top-right corner of the platform to get started. If the option is disabled, request access and our team will follow up with next steps.
Request access
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digibee.com/documentation/development-cycle/digital-worker-mode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
