Three rooms. One workshop.
Every tab below is a feature we already shipped or have wired scaffolding for. No vapor. No fluff. Browse before you sign up.
Every tab below is a feature we already shipped or have wired scaffolding for. No vapor. No fluff. Browse before you sign up.
Network isn't a directory. It's a matchmaking surface for builders who want operators, mentors, and pod-mates, without the LinkedIn shtick.
Tell us what you're shipping. We'll surface 3 people in this community working on adjacent problems.
Office-hour-style rooms hosted by senior practitioners — sign up for 25 minutes, leave with a real answer.
Small groups (3-5) collaborating on focused agentic AI projects with clear scope and 4-week cadence.
The awakening
Three rooms in the workshop. Pick where you start — learn, discuss, connect. The community pulls the rest forward.
The frameworks and disciplines behind agents that go from “works in a notebook” to “works under load.” Each primer goes deep on one; the ladder below shows how they fit together into a production stack.
Built for people breaking through the talking points and buzzwords and getting to actual collaboration alongside engineers who deploy agents in enterprise settings every week. No fluff, no hype loops, no influencer feed.
Founder note
AgenticWorks is the workshop I wanted when I first tried to put an agent into production and realized the gap between “works in a notebook” and “works under load with three other agents in the loop” was several disciplines wide. The mission is simple: grow a curated community of engineers who ship agents, then make it easy for everyone else to learn alongside them.
AgenticWorks Founder
The discipline ladder
Six disciplines that turn a working prompt into a deployable agent. None of them are optional in production.
Monthly live builds + archived recordings
Forum
Threads tagged by stack, 48-hour answer SLA
Office hours
Weekly rooms with senior practitioners
Pods
Small open-source crews on focused 4-week sprints
Tighten the input. Constrain the output. Get repeatability before reaching for scale.
Manage the window. Summarize, compress, and route; long context is a budget, not a feature.
Wrap the model. Tools, structured outputs, retries, and guardrails turn an LLM into something callable from real code.
Retrieve the right truth. RAG isn't one pattern: PDFs, tabular data, and tables-on-PDFs each demand a different stack. Match the data shape with embeddings, rerankers, or hybrid.
Wire the loop. Planner → worker → critic. State machines beat free-form agent improv every time.
Trust by measurement. Golden traces, regression suites, and online dashboards: ship what you can prove.
Prompt eng
Tighten the input. Constrain the output. Get repeatability before reaching for scale.
Context eng
Manage the window. Summarize, compress, and route; long context is a budget, not a feature.
Harness eng
Wrap the model. Tools, structured outputs, retries, and guardrails turn an LLM into something callable from real code.
Context RAG
Retrieve the right truth. RAG isn't one pattern: PDFs, tabular data, and tables-on-PDFs each demand a different stack. Match the data shape with embeddings, rerankers, or hybrid.
Orchestration
Wire the loop. Planner → worker → critic. State machines beat free-form agent improv every time.
Eval & obs
Trust by measurement. Golden traces, regression suites, and online dashboards: ship what you can prove.
The workshop where engineers go from buzzwords to working agents alongside teams shipping at enterprise scale.

Memory in production
Short-term scratchpads, long-term knowledge stores, and session boundaries each solve different problems. Treating chat history as memory is why your agent forgets what mattered.

Microsoft stack
AutoGen taught Microsoft conversation loops; Semantic Kernel taught it enterprise plumbing. The Agent Framework is the merger, and the migration story matters more than the feature list.

Conference watch
Cloud Next was less about a new model and more about where agents run, who governs them, and how they get discovered inside an org. Here's what Agentspace and the ADK push mean for enterprise buyers.

Orchestration patterns
Letting agents riff produces great demos and terrible audits. Explicit planner–worker–critic loops encode rejection at the orchestration layer. The same move as scaling-your-no, but structural.