Hi, I'm Jaros,
I run AI agents
sharing my setup via wellgent.ai
The layers every personal agent is built from.
model · harness · runtime · context · surfacesWhat each approach builds, and what it takes off the shelf.
five approaches, fully custom to packagedOne brain repo, many agents, as I run it.
Claude Code · Codex · OpenClaw · HermesEveryone is building personal agents. Everyone means something different.
Your code calls the model API and runs the tools.
built on: the model API, any modelYour app wraps a library that runs the loop.
for example: Claude Agent SDK, LangGraphYou define the agent and the vendor runs it.
for example: Claude Managed Agents, OpenAI Agents APIYou give a ready runtime your instructions, skills and tools.
for example: Claude Code, Codex, OpenClaw, HermesYou sign up and use the agent as it ships.
for example: Instinct, Meta Muse, Grok BotIt starts with a model.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
A harness turns a model into an agent loop.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
A runtime puts the harness to work.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
Use a ready runtime, or build your own.
Context gives the agent your world.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
Surfaces are where people meet the work.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
An agent is a slice through the whole stack.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
A different slice makes a different agent.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
Or define your own agent on a service.
Memory
What the agent knows about your world
Instructions
Standing behaviour and limits
Skills
Step-by-step know-how for a task
Tools
Actions on your systems and data
Workflows
Recurring work and what triggers it
Every approach builds different layers.
One setup,
as an example.
My own: one brain repo, many agents.
On my Macs.
terminal · Claude appOn my Macs.
terminal · Codex appOn my brain server.
Discord · TelegramOn an always-on Mac.
Telegram · SlackHow I decided what to build
Own my context
Knowledge, processes, skills and routines live in my repos, in plain markdown. No vendor holds them.
Don't build what others build
Harnesses and runtimes get better every month. I take them and spend my time on the context.
Use subscriptions
My Claude and ChatGPT plans run every agent, instead of paying per token on the API.
Test any new agent
Too early to call winners. A new harness or runtime gets pointed at the same core and tried out.
I rent the engine. I own the context.
Memory
Markdown pages, indexed into Postgres on my brain server
Instructions
The rules and routing every agent follows
Skills
Packs I adopt, plus skills I wrote
Tools
Existing tools, plus my own scripts
Workflows
My processes, and the crons that run them
How the whole set fits together
- AGENTS.md and rules
- skills and workflows
- pages
Rent the engine.
Own the context.
Turn your phone sideways to read the slides.