Your first agent
Turn a job worth repeating into a teammate.
You just ran a job in a thread and steered it right. An agent makes that the starting point instead of something you rebuild: a named teammate carrying the instructions, tools, and knowledge the job needs, into every future run.
Don't design an agent. Promote a thread.
The best first agent already exists: it's the thread where you just corrected the work into shape. Hyperagent reads that conversation and drafts the agent from it, so the briefing you refined becomes the agent's standing instructions.
Promote the thread
Save the thread as an agent
In the thread where the work went well, open the … menu in the header and choose Save as agent. Hyperagent reads the conversation, analyzes the patterns, and generates a draft: name, description, and instructions, all taken from how the work actually went.
Review what it wrote
The draft opens in the agent editor with everything pre-filled and everything editable. Read the instructions like a job description: is this what you'd tell a new hire doing this job?
Create it, then run it once
Click Create Agent, then start a new thread with the agent and give it the same kind of job. It should land close to where your corrected thread ended up, without the corrections.
Starting from scratch works too: New agent from the Agents list gives you the same editor, blank. Reach for it when the job exists only in your head, not in a thread yet.
What makes a good first agent
- A job you did this week and will do again. A weekly summary, a report format, a research routine. Recurrence is what pays for the setup.
- One job, not a department. "Writes renewal briefs" beats "handles customer stuff." You can always make a second agent.
- Instructions that would brief a person. The draft gives you a start; sharpen it with the two or three rules you found yourself repeating in the thread.
What the agent carries, and what it doesn't
The agent brings its identity, instructions, tools, and knowledge into every new thread. It doesn't bring the old thread's conversation: each run starts clean, which is what keeps run fifty as sharp as run one. What should persist between runs becomes a memory or a skill, and that's the next lesson.
FAQs
Next: teach it something it'll never forget. Teach it something →