Agent Builder

The Agent Builder is one page: everything an agent needs, then Deploy. Open it from Agents → New agent; the Agents page lists every agent in the workspace. Editing an agent opens the same page and redeploys the same agent - same id, same embed snippets and API calls.

Basics

• Name - shown everywhere in backcrew. You can rename it later.
• Model - from the models your workspace offers, each with its price per 1,000 tokens. You pay for the model the agent actually calls.
• Region - where the agent runs. It’s fixed once the agent exists. Tools and knowledge bases must be in the same region.

Code

A Python project in a multi-file editor:

• agent.py (or the file you mark as the entry) defines agent = Agent(...) using the Strands Agents SDK.
• Add more files and import them by name.
• requirements.txt lists extra packages from PyPI, one per line.

backcrew adds the plumbing around your code - memory, tools, knowledge search, policies and usage metering - so your code stays about what the agent does.

Builder assistant

• Describe your agent - explain what it should do in plain words; the assistant writes the code and suggests tools, knowledge and memory from what your workspace has. You review before deploying.
• Fix with AI - after a failed deploy, the assistant reads the error and proposes a fix.

The assistant is charged on the tokens it uses (see Credits).

What the agent can use

Field	What it does
Tools	Your workspace’s tools this agent may call.
Knowledge	Up to 5 knowledge bases it can search and cite.
Policy	The policy it follows - topics it won’t discuss, actions it never takes.
Quality checks	A set of checks scoring a sample of its answers. Off by default.

Advanced settings

• Memory
  • Off - every message starts fresh.
  • Session - remembers the conversation while it’s open (the same session).
  • Persistent - also keeps a long-term record of each person’s conversations.
• Code Interpreter - a sandbox where the agent can run Python, for calculations and data work.
• Browser - a cloud browser the agent can use to read websites, optionally limited to sites you list.

Deploy and status

Status	Meaning
Building	Creating the runtime and everything it uses.
Deployed	Live and answering.
Updating	Saving your changes. The agent keeps answering with its current version until the new one is ready.
Update failed	The changes couldn’t be applied, so the agent is still answering with its previous version. The agent page shows why; fix it and save again.
Failed	The first deploy went wrong, so the agent isn’t answering yet. The agent page shows the error; fix it and save again.
Deleting / Deleted	Being removed / removed, with everything it used.

Saving changes never takes a live agent offline: the dashboard, API, website widget and Telegram keep getting answers throughout.

You can also start from a Marketplace template: it becomes an ordinary agent you can edit.