Unclear autonomy
Define what the agent may decide, suggest, call, change, or escalate.
Design AI agents that use tools deliberately, manage context, coordinate workflows, and return control to people when the work needs judgement.
Builders need to reason about planning, memory, context, permissions, multi-agent handoffs, failure paths, and the human decisions that must remain visible.
Define what the agent may decide, suggest, call, change, or escalate.
Choose the right context and memory pattern without filling the workflow with irrelevant history.
Understand when planning, specialist agents, or human-in-the-loop patterns make sense.
Build and test a bounded agentic workflow with explicit tools, controls, and deployment notes.
Choose triggers, goals, tools, context, planning, and handoffs for a clear system boundary.
Give agents useful tools and context while keeping permissions and outputs constrained.
Compare memory, context engineering, specialist agents, and orchestration choices.
Review evaluation, observability, safety, deployment, and human-in-the-loop controls.
Programming and LLM application familiarity are useful. The course treats permissions, failure handling, and human ownership as core engineering work.
Choose a support, research, knowledge, operations, or engineering workflow where tool use and human review can be demonstrated.
Define the trigger, goal, tools, permissions, context, and non-goals.
Exercise uncertainty, tool errors, approvals, and escalation before the final demo.
Show a bounded run and explain how it would be evaluated and operated.
MHGrad’s practice includes agents, MCP, RAG, software delivery, operations automation, HR knowledge assistants, and customer-support workflows. Verified trainer credentials and references are available during enrolment conversations.
Ask about the next intensive, availability, payment steps, or private team delivery. Refund terms are published before payment.
MHGrad publishes the learner, role, cohort, project, exact words, and permission status when a story is approved. See the proof policy.
The course is developer-focused and benefits from programming and LLM application experience. Team versions can include product or operations roles.
Clear boundaries, tool permissions, evaluation, observability, failure handling, and a human owner are part of the design.
Discuss data access and confidentiality before enrolment. A non-confidential guided workflow is always available.
Eligibility, cut-off dates, transfers, and cancellations are stated in the refund policy and enrolment confirmation.
Ask for dates, fee, prerequisites, or a team-training conversation.