Meet Smith: A Legendary Resource to Run Your Agents at Scale

Every era has its builders. A few hundred years ago, they worked in forges.

Today, they build systems.

The great smiths of olden times weren't remembered for making swords. They were remembered for creating the tools everyone else depended on. Better plows. Better hammers. Better machines. When the smith improved, the entire community moved forward.

The same thing is happening with AI agents.

Teams are deploying agents into production. Agents create tickets, review code, answer customers, update systems, and move data across dozens of services.

The challenge isn't building an agent. The challenge is building the infrastructure around it.

Workspaces. Integrations. Credentials. Triggers. Permissions.

That's where Smith comes in.

It starts with one sentence in a blank chat.

Smith is Guild's platform builder. A meta-agent that helps you configure, deploy, and govern the agents that run your work. Describe what you want to automate. Smith assembles the pieces.

It builds new agents or installs existing ones. Creates workspaces. Configures triggers. Connects integrations. Requests credentials. Wires workflows together.

Not by bypassing controls, but by operating within them.

Every action runs through the same identity model, permissions system, and audit trail that governs the rest of the Guild platform.

And nothing happens without your say-so. Smith proposes, you approve. It shows you the full plan and asks before it builds. That is confirmation by design, not a setting you switch on.

The original smiths forged the tools of their era. Smith helps you forge yours.

Guild is built for running agents in production. Production systems have moving parts. Agents. Workspaces. Triggers. Integrations. Credentials. Permissions. Most users don't want to learn platform topology before automating their first workflow.

Smith removes that friction. Smith is a meta-agent whose job is not execution. Its job is orchestration.

You describe the outcome. Smith assembles the infrastructure.

Need a daily Linear summary posted to Slack? A morning digest of your unanswered emails, with draft replies?

Whatever it is, Smith does the same work:

• Builds a new agent, or installs one that already fits
• Creates a dedicated workspace
• Configures schedules and webhooks
• Requests the credentials it needs and waits for you to approve them
• Wires the agents together into a workflow

Here's Smith building an agent end-to-end. We picked a simple one to watch: a daily Hacker News briefing delivered to your inbox each morning.

Before it builds, Smith asks what it needs and assumes nothing else: whose account, what to read, how to deliver, when to run.

You grant access explicitly. The agent only gets the integrations you approve, scoped to this workspace.

Smith lays out the whole plan, workspace, agent, credentials, and trigger. Then it waits for your "yes" before touching anything.

Minutes later: a live workspace with the agent installed, the trigger scheduled, and a session ready to open.

The agents perform the work. Smith builds the system that enables it.

Smith doesn't stop once the system is built. It helps you run it. With Smith:

• See what it costs. Usage and token spend by workspace, by session, down to a single task.
• Find out why a run was slow or stuck. Smith reads the session and separates wait time from startup, tool calls, and model time.
• Step in when you need to. Interrupt a runaway session, or post a message into one.
• Check the record. A searchable audit trail of every action, on any account.

The meta-agent that builds your system also helps you operate it.