Skip to main content
In plain language, this page explains what must be set up around an agent: where it runs, which project it works on, and what it is allowed to do. If you are learning the basics, complete the beginner tutorials first. Release: 0.1.0a3. This is a setup reference for integrators, not an automatic provisioning command. An environment is the ownership boundary around an agent’s runtime, repositories, credentials, Instances, and memory. Installing PeopleBot supplies reusable code. You separately decide where it runs, which projects it can access, and what work it may do.

​
Keep the responsibilities clear

A repository identity is not a checkout path. An Instance identity is not an operating-system account. Record each binding explicitly rather than assuming matching names connect the resources.

​
Start with a small verified operation

  1. Install the exact release and retain its source and provenance.
  2. Complete the local State example.
  3. Assemble a small, explicit context selection.
  4. If you need the review adapter, use Windows and inspect the review prerequisites.
  5. Check execution evidence and any saved memory separately.
The synthetic alpha-setup, alpha-adopt, and alpha-resume utilities are not shortcuts for these steps. They demonstrate local mechanics with supplied fixture bindings.

​
One active execution per Instance

The v0 admission path uses a Windows file lock. Competing work for the same environment/Instance is rejected without launching its callback. Every launch path must use the same runtime-root binding for that local admission scheme to coordinate correctly. It is not a distributed lock across machines. Separate actors should use separate Instance identities. Copying a Blueprint into another environment creates the basis for a new actor; it does not transfer an existing actor’s credentials, memory, or permission to act.

​
Updating the framework

Treat a version label as a discovery aid and adopt the intended source commit and artifacts explicitly. Keep an active execution on its pinned implementation until it finishes. General cross-version migration is not provided by this release; the synthetic adoption example has a narrower compatibility contract.

​
Public reference

Environment adoption contract, Admission contract.