Community | Guild.ai
Welcome to the Guild
Where builders think together. Not in isolation. Not in silos. But as a Guild—like the ones that came before.
Guild ID Locations
G.ID 8278 BUILDING IN 41.8832° N 87.6324° W
G.ID 4512 BUILDING IN 37.7749° N 122.4194° W
G.ID 9103 BUILDING IN 51.5074° N 0.1278° W
G.ID 2847 BUILDING IN 40.7128° N 74.0060° W
G.ID 6391 BUILDING IN 48.8566° N 2.3522° E
G.ID 7024 BUILDING IN 35.6762° N 139.6503° E
G.ID 1856 BUILDING IN 52.5200° N 13.4050° E
G.ID 5439 BUILDING IN 43.6532° N 79.3832° W
The original guilds weren't just groups.
They were systems of craft. People sharing techniques, refining tools, raising the standard of the work itself. Guild brings that model into software.
Guilds used to be local.
Now they're everywhere.
If anything goes wrong with Kubernetes clusters, we need to be in an age where agents help to scour through logs and troubleshoot, not us. Follow along in this hands-on with a local kind cluster and we'll show how easily you can get agentic troubleshooting going with Guild. Most importantly, you'll see how Guild's agents are properly credentialed and cannot access anything that you haven't approved.
Hack of Horrors
October 30, 2026
9:00 AM PDT
Online
Mwa-ha-ha! Something wicked this way deploys. On October 30th, build the bot of your nightmares: give it a brain with Guild agents, keep the skeletons out of your code with Snyk, and let it haunt Render 24/7. Treats include up to a year of Discord Nitro and 100M tokens.
Find a Forge near you.
The Guild meets in cities around the world. IRL and virtually.
Start Building in Minutes
Deploy your first agent, scope permissions, connect your stack. Real code, real governance.
Get running in under 5 minutes
# Install the Guild CLI
$ npm install -g @guild/cli
# Initialize your workspace
$ guild init my-workspace
# Deploy a code review agent
$ guild deploy agent/code-review \
--scope github:my-org \
--budget $50/day
# Agent deployed. Monitoring active.
✓ code-review-agent is live
Learn from the Guild
The best work doesn't stay hidden. Guild is built on shared knowledge: patterns that hold up, tools that actually work, ideas tested by your peers. You don't just consume it—you add to it.
Agent and Integration Hub
Browse and deploy pre-built agents for code review, security scanning, incident response, and more. Start with a template, customize for your stack.
Guild Docs
Technical documentation, API references, quickstart guides, and everything you need to build, deploy, and govern agents on Guild.
Guild YouTube
Product walkthroughs, quickstarts, and conversations with engineering leaders about what’s actually working with AI agents.
Build Together
The work gets better when people do. Guild exists to make that happen.
Slack
Real-time conversations with the Guild team and community.
Coming soon
Discord
Share agents, discuss patterns, and connect with the community.
Be part of the conversations shaping the future of AI. Connect with engineers sharing real-world lessons and experiences.
From the Discord community
Real conversations from members building on Guild.
xhale22b_35008
Is task.env.create() / task.env.exec() available in the current SDK? We need to run a Node.js shell command from inside an agent's run() function. We're hitting the Babel state machine limitation with native https module calls.
Jedweb3
Amazing workshop and use cases. looking forward to the recordings.
Claim your Guild ID
Every member gets their shield.
Apprentice
Builder
Artisan
Master
Questions? Start here.
What is an agent control plane and why do engineering teams need one? An agent control plane is the infrastructure layer that governs AI agents in production. Guild's is built on four primitives: workspaces that contain agents and their policies, organization-level credentials injected at runtime, sessions that log every run, and triggers that automate execution. Without one, every agent holds its own keys, runs without an audit trail, and spends without attribution. A control plane replaces that sprawl with one place to see, control, and account for every agent.
How does Guild handle permissions and access control for AI agents? Guild scopes access structurally rather than by role labels. Credentials are connected once at the organization level and injected at execution time, so agents never hold raw keys. Workspace-level policies decide which teams and agents can use which integrations: a support workspace cannot reach engineering's GitHub credentials. Model policies follow a hierarchy from account to workspace to agent, and disconnecting a credential instantly revokes access for every agent that used it.
How does Guild enforce budget limits on AI agents? Guild enforces hard limits, not advisory ones. A daily token limit caps LLM consumption: once the limit is exceeded, further LLM requests are rejected for the rest of the day. Model policies control which models an API key can call, applied hierarchically from account to workspace to agent. And because every session records the model and token count of each LLM call, spend is attributable per agent before it ever becomes an invoice surprise.
How quickly can a new team deploy their first agent on Guild? The fastest path is installing a pre-built agent from the Agent Hub, where teams publish validated agents like ticket triage and PR review, ready to run in your workspace. Building your own is three CLI steps: scaffold with guild agent init, test locally with guild agent test --ephemeral, then publish with guild agent save --publish. Either path gets a first governed agent running the same day you start, typically within minutes.
Run. Control. Transform with Guild.
See Guild in action.