Smith

• Smith is Guild's built-in support and assistant agent. Every new user meets Smith through the /onboarding tour, and every workspace opens directly into a Smith chat.
• Smith's fully qualified name is guildai~the-smith. It behaves like any other Guild agent — same governance, same session model, same audit trail — but it ships with the platform.
• Smith is what makes Guild useful before you configure anything. Type a message and press Enter, or @mention another agent to hand the conversation off.
• Smith runs inside the same runtime as your own agents, so anything Smith can do is a preview of what a coded, LLM, or Goose agent on Guild can do for your team.

Smith is the built-in agent that ships with every Guild account. It is Guild's answer to the first question a new user always has: what do I actually do first? Instead of a blank editor or an empty workspace, Smith gives you a working agent to talk to from the moment you sign in.

Its qualified name is guildai~the-smith, the same owner~agent-name convention every other Guild agent uses. Under the hood Smith is an ordinary agent: it runs in a workspace, produces sessions, respects credentials and workspace context, and shows up in the same session lists and audit trails as anything else you deploy on Guild.

The name is deliberate. Smith is the assistant you go to first — the one that helps you set up, learn the platform, and route questions to the right specialist agent as your team builds them.

The onboarding tour is the entry point

New Guild accounts start in the /onboarding tour. The tour introduces the platform and offers a set of starter prompts. Selecting one submits it to guildai~the-smith and opens a real session, so the first thing a new user experiences is an agent doing something useful, not a configuration form.

Every workspace opens into Smith

After onboarding, opening a workspace takes you straight to the Smith chat. Whenever you have no active session, /chat is Smith. Type a message and press Enter to start a new session, or use @mention to route a message to a different agent instead.

Smith is a normal agent, not a hardcoded UI

Smith runs on the same runtime as every other agent on Guild. Its sessions show up in guild session list, it can be inspected with guild agent get, and it obeys the same workspace credentials and context that govern any other agent. There is nothing magic about it. That is the point.

Hand off to a specialist with @mention

You can start a conversation with Smith and, mid-thread, route the next message to a different agent by @mentioning it. The session stays with Smith, but the specialist gets its turn on the specific question that requires it. This is the multi-agent pattern Guild is built around, made accessible from the default chat.

Time-to-first-session should be zero

Most agent platforms make you configure something before you can see anything happen. Smith flips that. You sign in, you see a chat, you send a message, an agent responds. If it takes ten minutes to feel useful, most people never come back. Smith exists so that time is measured in seconds.

Smith is a demo of the runtime that never gets stale

Every improvement to Guild's runtime — new tool integrations, better session management, improved credential handling — shows up in Smith automatically. That means Smith is always the fastest way to feel how Guild has evolved without reading a changelog.

A default agent lowers the bar for specialists

With Smith handling the general case, teams don't need to build a generalist assistant of their own before they can build the specialist agents that actually earn Guild its keep. Ship a code review agent, a release notes agent, a customer-context lookup agent — Smith covers everything else.

Start a chat with Smith

guild chat                     # Opens The Smith

guild chat opens Smith in interactive mode. You can also open Smith from the app: any workspace with no active session drops you straight into the Smith chat.

Route to a specific agent mid-conversation

@mention any published agent in your workspace to hand it the next message: @owner~agent-name Ask something specific. The rest of the session stays with Smith.

Inspect Smith like any other agent

guild agent get guildai~the-smith        # Get agent detailsguild session list --agent guildai~the-smith  # List Smith sessions

Smith obeys the same guild session, guild agent, and workspace commands as anything else on the platform.

Smith is the default, not the ceiling

Smith is a great generalist. It is not a substitute for the specialist agents your team builds. Use Smith to get started, to learn the platform, and as a router. Build purpose-built agents for the work that actually needs domain-specific behavior, credentials, and prompts.

Smith runs in a workspace

Smith sessions live in a workspace like any other session. That means workspace context applies to Smith too. If your workspace has a strong shared context, Smith responds accordingly.

Smith is not a support ticket system

Smith is an agent you can talk to, not a queue that routes to Guild's support team. For product help and account questions, use Guild's support channels. Smith answers the questions an agent can actually answer.

Guild is a control plane for AI agents, a place to build, deploy, and govern the agents your teams run in production. Smith is what makes Guild useful the moment you sign in, and it evolves as the runtime evolves.

• The getting-started guide for The Smith walks through the /onboarding tour and the default chat experience.
• Smith lives inside a workspace like every other agent on Guild.
• Sign in at app.guild.ai to open the /chat with Smith yourself.