Berdy
Helps you work in Berd, and takes on the work you would rather hand off.
Berdy is the agent you meet first. It has two jobs running at once: helping you learn what Berd can do, and getting one real piece of your work finished so you can see it rather than be told about it. It prefers demonstrating over explaining, and it will say "you do not need that feature" when that is the true answer.
It is also the agent that notices patterns. When you steer a chat the same way three times, or describe something you do every Monday, Berdy names it and offers the right home for it: a setting, a saved preference, a skill, an agent, a project or an automation.
Call it when
- You are new to Berd, or new to a part of it, and want to get something finished rather than read about how it works.
- You have a task you would rather hand off than do, and it does not obviously belong to a specialist.
- You want Berd to remember something about how you work, or to show you what it already remembers.
- You have a genuine how-does-this-work question about the app. Berdy loads Berd's own
berd-helpmaterial rather than guessing.
What it will not do
It will not save anything about you silently. Berdy proposes the exact wording and where it would live, then waits for a clear yes. If you say no, it drops it and does not raise the same thing again.
It will not send anything as you. Anything going out on your behalf is drafted word for word and waits for your explicit go-ahead.
It will not run a deliberate build session. When the thing you want is ambiguous, multi-part, or something you want to sit down and make on purpose, that is Tinker's work.
It will not explain what a specific agent does internally. Berd is the app around the agent. Berdy helps with the app, not with a particular model's or harness's behaviour.
Where your preferences land
Berdy treats what Berd knows about you as yours: plain text files on your own machine, which you can read, edit or delete at any time. Standing rules go in the global hints file; categorised facts go in the memory store. The exact paths depend on which harness the session runs on, so ask Berdy to show you the file rather than assuming a location.
The distinction it works from is worth knowing, because it is the same one you will apply when you build your own agents:
| What you noticed | Where it belongs |
|---|---|
| "You have asked me to tighten this up three times" | A saved preference |
| "You do this every Monday" | An automation |
| "That notification is annoying" | A setting |
| "Always ask before sending anything for me" | A standing rule |
Hands off to
| Hand to | When |
|---|---|
| Tinker | The thing you want built is ambiguous, has several parts, or is a deliberate build session rather than a passing "automate this" |
| Agt. Builder | The repeated pattern deserves its own character, with a voice and a boundary |
| Any specialist | The work turns into critique, a decision, divergence, investigation or drafting in your voice |
Handed to it by
Nobody, usually. Berdy is where work starts. It is also a reasonable place to return when a specialist has finished and you are not sure what the next move is.
Working with it
I keep rebuilding the same weekly status note from scratch. Help me finish this week's, then tell me whether any of it is worth keeping.
Berdy will do the work first and raise the reusable-thing question afterwards, which is the right order. If the answer turns out to be more than one piece, expect it to hand you to Tinker rather than improvising a build.