← Back to library

Give a work agent its own login, mailbox and diary

mike_hearn on Hacker News combined Codex on a paid ChatGPT plan with systemd plus plain Unix mailboxes and user accounts so the agent handles assorted company tasks much as a staff member would. For memory, one long-running container keeps a diary rather than opaque chat history.

  • OutcomeRun an autonomous helper like a junior employee by giving it a dedicated system user, an email address and plain-text memory files it maintains itself.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditmike_hearn on Hacker News
View original
Works with
Custom agentChatGPT

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You want an agent that works between your requests
  • You are comfortable administering a Linux box
  • Tasks arrive by email anyway

Not for: Teams without anyone to watch the logs; Work involving payments or customer data at first

What do you need, and what do you get?

You need

  • A dedicated machine or VM
  • A system user and mailbox for the agent
  • A wiki folder

You get

  • Tasks handled from email
  • A daily diary of work done
  • A growing wiki of how things are done

How does it work, step by step?

  1. Create a separate userGive the agent its own account with only the folders it needs.
  2. Give it an addressSet up a mailbox so you can send tasks the way you would to a colleague.
  3. Keep it runningUse a service manager so the loop restarts after crashes or reboots.
  4. Memory in filesHave it keep a diary and a wiki of procedures it can reread.
  5. Review the diaryRead the diary daily at first and correct anything odd.

The prompt

Our own prompt, inspired by mike_hearn on Hacker News and written to work in Custom agent and ChatGPT. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You are {agent_name}, working for {company} from your own account.
Check your mailbox for new tasks. For each: restate it, list what you will do, do it within your permissions, and append a diary entry with what changed and any open questions. Ask by email before anything involving money, customers or deleting files.

Inspired by mike_hearn on Hacker News: Hacker News comment on a self-built autonomous agent for company work. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A shared login with your own account removes any boundary; keep it separate.
  • Memory files grow messy; ask it to tidy them weekly.

Our take

Treating the agent as an employee with its own account is an old idea that suits new tools: Unix users, file permissions and mail already provide identity, isolation and an audit trail. The diary is the part we would copy first, because it is readable and versionable. Give the agent its own login. Separate personal and work agents. mike_hearn's setup uses ordinary pieces: a separate Unix user with access only to the folders it needs, a mailbox so you can send tasks the way you would to a colleague, and a service manager that restarts the loop after crashes or reboots. Read the diary daily at first and correct anything odd, and ask the agent to tidy its memory files weekly. Keep payments and customer data out of scope until it has a track record. Never let it share your own login; a separate account is the whole point, because it gives you a boundary, file permissions and a clear audit trail of what the agent touched. Someone needs to watch the logs.

Where the time goes back: Small company chores get picked up from email without you starting each one.

FAQ

Has memory been a problem?
Not so far for the author, though he notes it is early.
Should I run several?
He is considering specialist bots, the way you would hire specialists.

Source and credit

Inspired by mike_hearn on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Hacker News comment on a self-built autonomous agent for company work
Creator
mike_hearn on Hacker News
Published on
Hacker News
Original date
Apr 11, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Build a first web app as a non-coder, one model per job

Split a weekend app build across tools: an app agent for the scaffold, one model for requirements, another for fixes, and expert review before charging anyone.

Credit: u/mrcsvlk on r/replit

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Plan App Store review time for an AI-built app

Draft the store-release checklist (account, signing, listing text, images, plan names) early, because review rounds can take longer than coding.

Credit: u/Adventurous-Win-1489 on r/replit

Under an hour
Operations & AdminWorkflow✓ AI dry run

Give each business function its own reviewing agent

Cover finance, tax, legal, marketing and ops as a solo founder, with agents that check each other before anything goes out.

Credit: João Pedro Silva Setas

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Let a calling agent ask you questions mid-call

Give a terminal agent a phone voice, plus a live dashboard where it routes questions it cannot answer to you without hanging up.

Credit: BOOTOSHI (@KingBootoshi)

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Merge overnight mail, meetings and tasks by 7am

One short morning brief per person that points to prep, replies and the day's important tasks, instead of starting in five tools.

Credit: u/Cnye36 on r/AI_Agents

Under an hour