What you leave with
- Hermes running on your own server, with Claude as the configured model
- MCP servers connected for the tools you actually use
- Scheduled jobs that report somewhere your team will read
- Keys kept out of shell history and out of the repository
- A way to let colleagues use it without giving them the server
Day one
| Block | Content |
|---|
| 09.00–10.30 | Installation, provider configuration, first conversation |
| 10.45–12.00 | Model selection and cost behaviour: what a job actually costs |
| 13.00–14.30 | MCP: connecting tools, reading what the agent can reach |
| 14.45–16.00 | Practice: a job that checks something real and reports it |
Day two
| Block | Content |
|---|
| 09.00–10.30 | Schedules, webhooks and delivery to chat |
| 10.45–12.00 | Giving the team access without handing over root |
| 13.00–14.30 | Guardrails: destructive actions, approvals, audit trail |
| 14.45–16.00 | Bring your own use case, built with assistance |
Bring a real problem. The second afternoon works far better when you bring
a task your team repeats weekly. People who arrive with one leave with something in use.