Questions before your first workflow.

Not for everyday use. A partner can handle technical setup and connect your systems. You define the work, rules and approval boundaries.

A chat usually begins with a question. A workflow has a defined ongoing responsibility and responds to new material or scheduled tasks. You do not need to describe each step again.

Yes, if the engine runs on another available machine, such as your server. Switching off the computer that runs the engine also stops its work.

Set permissions and approvals for sensitive actions, review outputs and handle exceptions. Autonomy does not mean infallibility or a transfer of professional responsibility.

Working context and files live in your environment. The app and engine communicate with end-to-end encryption; neither the relay nor the central backend decrypts this working content. Account and subscription data are separate. External models and connected tools receive the inputs your agenda sends them.

They can improve methods and knowledge only within the limits you set. They do not change fixed goals, prohibitions or approval boundaries themselves, including during repairs or updates. You can also close an agent’s entire instructions to automatic rewriting. You change the fixed rules.

Yes. Agents, tasks, conversations and settings are readable files in your project. Open them in an ordinary editor, back them up or move them elsewhere. By default, Promptbook records completed changes in Git, so you can see earlier versions too.

Yes, within the supported harnesses and models. Your roles, rules and files stay in your project. A local model requires a compatible harness integration and suitable hardware; check its quality and ability to use tools on your own workflow. External tools may still send data out when you use a local model.

In the app, you assign work through chat and can start, pause, resume, stop or restart a project. Open the local dashboard directly on the engine’s host without pairing; remote control uses an authenticated, end-to-end encrypted connection.

The engine continues under your rules on its available host after you close the app, sign out or lose a device. An unavailable connection does not itself mean the project has stopped. A manual pause suspends automatic work while keeping chat and controls available; stopping ends the engine’s run.

By default, the engine installs stable patch and minor releases within the same major version when it has free capacity. You can disable automation or pin a version. Prereleases are not enabled automatically; if you are already on one, you follow it to its stable release and then stay on stable releases. Manual pause and stop remain in effect.

The app gives you a command for your VPS. After connecting, continue setting up your first agenda and signing in to your chosen AI tools. You complete sign-in in a protected interface or terminal; passwords and login codes do not go in ordinary chat. A partner can help with deployment.

The public code has its own licence terms. Independent development and non-production testing have no licence fee under the applicable version's terms. Production use follows that version's rights and any Start or Business commercial licence.

Licences are charged per engine project: a separate working environment with its own agents, rules and permissions. A workflow is an example of use, not a licence boundary. Each additional project has its own subscription; one customer may combine Start and Business projects. Physical servers and the customer company as a whole are not the licence unit.

A specialist agent is an activated working role in a project. It occupies a place even while waiting for work. Archived definitions and templates do not count; replacing a role does not create another full monthly charge. Core and system roles for communication, routing, learning and repairs do not use specialist places. The actual function, rather than the role name, determines the count.

A controlling user is an identifiable person authorised to assign or change project work. Multiple devices used by that person still count as one user. An agency technician counts in the same way as a customer employee. Report and other output recipients, and merely contacting manufacturer support, do not count.

A harness instance is one active connection with its own configuration and authentication context. Multiple tasks or sessions using the same connection do not increase the count. Start includes one instance; Business has no licence count limit. AI provider terms, limits and charges apply separately.

A browser profile separates a signed-in identity. One profile may use many websites; individual websites, tabs and integrations do not count separately.

Business add-ons are charged for capacity above the included allocation, proportionally to the time it is active during the billing period, rather than utilisation, messages or responses. Half a period costs half the monthly rate. Paid expansion requires the customer’s explicit prior approval and an agreed monthly budget. The default is no automatic overage: a warning precedes the limit, unapproved paid capacity is not activated and the price does not change automatically. Reaching a capacity limit does not cancel tasks already in progress. Billing is supported by a reviewable record of capacity and activation time.

Start can be used long term. More capacity is available by upgrading to Business. An upgrade retains the same project and data and requires confirmation of the paid change. A downgrade starts at the next billing period once the project meets Start limits. Plan changes and add-ons do not restart the 24-month commission window.

No. Business includes a first substantive response within 16 working hours in the defined support window, not continuous on-call support, a repair guarantee or an uptime guarantee. See pricing for details.

A partner helps select the workflow and handles setup and routine care as agreed. Promptbook provides the technology and licensed product support. Independent technical deployment is also possible.

Not necessarily. Compare the approaches. Some tools, such as coding harnesses, can form part of your Promptbook solution.