Agent Development

Brazosd is an agent platform that provides many agent capabilities and will provide more infrastructure over time. Users can build powerful agents by using the capabilities provided by the platform.

Cloud Drive

Agents can use Brazosd cloud drives. Cloud drives currently have several scopes: organization drive, channel drive, session drive, and user drive.

An organization drive is shared within an organization. Agent-specific business materials, generated artifacts, and reusable context live under @brazosd://org.drive/<org-id>/agents/<agent-id>/.

A channel drive is shared by all members in a channel. When an agent is a member of a channel, it can access that channel's drive.

A session drive is persistent file storage associated with one session, for attachments and deliverables. Agents save results to the current session drive by default, or to another location requested by the user. Inactivity expiry and manual archival retain cloud files for the user to manage and delete; archival still destroys the work sandbox. A fork starts with a new empty drive, while existing files remain accessible at their original session paths according to the user's permissions.

A user drive belongs to the user. An agent session acts with the current user's Cloud Drive permissions and can operate that user's drive, owned session drives, the organization drive, and channel drives where the user is a member.

An agent factory repo is a special resource. The running agent can read its own repo, but can write it only while serving the organization that created the repo. When an organization recruits a third-party agent, that agent's own repo is read-only and the consumer user cannot access it directly. This exception does not remove the session user's access to other agent repos created by their organization.

The brazosd_ctrl Tool

The brazosd_ctrl tool allows an agent to access all Brazosd features using the user's identity.

It is in the default tool set for every agent. API operation paths listed by /openapi.yaml are mounted below /api/v1; for example, call the listed /agents path as /api/v1/agents.

With this tool, an agent can operate the platform itself as a business system, such as reading session information, handling channel context, managing platform resources, or composing other platform capabilities into its own business workflow.

Secure Variables

Agents use secure variables through special character forms. When the Brazosd kernel intercepts tool calls, it translates those special characters into the corresponding variables.

Secure variables are stored in encrypted storage. After a variable value is set, the plaintext value cannot be viewed in Brazosd.

If an agent wants to request sensitive information such as a verification code or password, it can start a built-in tool call and ask the user to fill it in. After the user fills it in, Brazosd can provide that information as a secure variable for later tool calls instead of exposing plaintext to the agent or to the large model context.

Agent Memory

Developing general-purpose agents is not currently a goal of Brazosd, and Brazosd does not currently provide an officially supported agent memory mechanism.

Brazosd is designed as a platform for building enterprise-grade expert agents, and it favors developing agents for specific business domains. Users can build business-specific memory modules by storing agent context under the agent's organization-drive directory and by using brazosd_ctrl to access session information.

Sandbox

Each session has an isolated virtual-machine-based work sandbox. After the work sandbox has not been used for a period of time, it enters sleep mode, and only a small amount is charged for the storage space already used.

To fully destroy a sandbox, the session must be archived. Archived sessions cannot be continued with follow-up questions.

Sandboxes are created lazily. This means that after a new session is created, if no sandbox command is run, the sandbox will not be created. For short sessions awakened by events, avoiding sandbox creation can reduce task duration and storage management cost.

Devices

Agents can operate connected devices through the Brazosd encrypted tunnel.

Agents can operate multiple devices and sandboxes at the same time. Brazosd will gradually support more smart devices such as Android, macOS, and iOS in future versions, and will provide an RPA framework for GUI devices.

Device Background Tasks

Agents can use the exec_command and write_stdin commands to open PTY processes on devices and run background tasks.

If a device does not support PTY, such as older versions of Windows, the agent can only use shell_command to run foreground tasks.

Sandbox background tasks will be supported in future versions. Currently, only devices support background tasks managed by the device connector.