Open source · runs on Herdr · early preview

Wheems: Your own little cloud of helpers.

Wheems is an open-source framework for teams of AI agents that take on any kind of work: answering support email, replying to reviews, planning the week’s posts, looking after your SEO, or shipping code. Hand your chief of staff a job from Slack. Its crew does the work, keeps to the guardrails, and only asks you when it matters.

See what it can do Follow @mikejdeeming

What your helpers can do

Not just code. Any work you can describe.

Each job is a workflow: something starts it, the crew does the steps, and anything that matters waits for your tap. Once a job has earned your trust, you can let it run by itself. To make a new one, ask the chief of staff.

Support inbox
When a new email reaches support@
Sorts each one (question, bug, refund or spam), answers questions from your knowledge base, and logs bugs for the developer.
Waits for you on refunds, and anything it isn’t sure about
Reviews
When a new review appears on Google or Trustpilot
Drafts a reply in your brand voice, and flags unhappy customers so nobody slips through.
Waits for you on every reply, until you’re happy to let it post
Social media
When it’s Monday at 9
Turns last week’s work and wins into posts for X and LinkedIn, checked for facts and tone.
Waits for you on the week’s posts, before anything goes out
SEO and content
When the weekly check comes round
Checks your pages and rankings, fixes titles and descriptions, and drafts the next article.
Waits for you on publishing
Bookkeeping
When an invoice lands in your inbox
Files it, matches it against the bank feed, and chases invoices that are overdue.
Waits for you on any payment: the agent prepares it, you pay
Code
When you ask in Slack
Builds the fix in its own terminal, opens a pull request, and has an agent from another provider review it.
Waits for you on the merge

Wheems is an early preview. Chatting with a chief of staff from Slack, and a knowledge base it keeps up to date, work today; email, review and social integrations come in later milestones.

What it’s made of

Five layers, one install.

You talk to a chief of staff. It hands the work to the agents you already use, unchanged, with skills, rules and a knowledge base scoped to the workspace, every one live in its own terminal on Herdr.

Works with

Claude Code
Codex
opencode
Slack
Telegram
Herdr

How it fits together

Any job, the same seven steps.

Whatever the work, a workspace runs it the same way. Pick a job and watch it go through, or pick a step.

Seven steps, from the first trigger to the knowledge base.Watch one job go through a workspace.01 Trigger. Three new Google reviews arrive and start the reviews workflow.02 Brief. The chief of staff reads your brand voice and refund policy, and briefs support.03 Draft. The support agent drafts a reply to each review, live in Herdr.04 Guard. An £80 refund is held: refunds over £50 need you, by a rule outside the agent.05 Review. Codex checks every reply’s tone: a second provider checks the first.06 Approve. You approve the replies and the refund with one tap in Slack.07 Learn. The replies are posted, and the session ends with a note in the knowledge base.

#reviews Slack

Workflow · reviews3 new Google reviews: ★★★★★, ★★★★, ★★

Chief of staffDrafting replies. One asks for a refund.

Chief of staffPost 3 replies and refund £80 to Sam?✓ ApprovedDecline

Chief of staffPosted. Notes filed.

workspace · side-projectworkspace · personal

workspace · acmerules enforced outside the agent

Chief of staff

Claude Code · knows every project here

Waiting for work3 new reviews in #reviewsRead brand voice · briefing supportSupport is draftingRefund held · needs youReviewer checking the toneWaiting on your approvalSession over · note writtenOne entry point for the workspace

Knowledge base

note
inbox
filing
pages

supportClaude Code

› reply to 3 new reviews
  draft in the brand voice
  ✓ 3 replies ready
$ refund order 4417 £80
✕ held: over £50 needs you
✓ sent to approvals

reviewerCodex

› check the tone of 3 replies
  warm, specific, no blame
✓ 3 of 3 pass

marketeropencode

  idle · role from a template

skills6 picked from a library of 120·versions pinned

Seven steps, from the first trigger to the knowledge base.Watch one job go through a workspace.01 Trigger. Twelve new emails reach support@ and start the inbox workflow.02 Sort. Each one is labelled: question, bug, refund or spam. Each label has its own action.03 Answer. Support answers the questions from the knowledge base; the developer logs the bugs.04 Guard. Spam is archived by itself, but the refund reply is held for you, by a rule outside the agent.05 Review. Codex checks every answer against your policies before anything is sent.06 Approve. You approve with a tap. Once a label earns your trust, it can run without asking.07 Learn. The session ends with a note, and new answers join the knowledge base.

#support Slack

Workflow · inbox12 new emails at support@

Chief of staffLabelled: 7 questions, 2 bugs, 1 refund, 2 spam.

Chief of staffSend 7 answers and the refund reply?✓ ApprovedDecline

Chief of staffSent. Notes filed.

workspace · side-projectworkspace · personal

workspace · acmerules enforced outside the agent

Chief of staff

Claude Code · knows every project here

Waiting for work12 new emails in #supportLabelled 12 · briefing supportSupport and developer workingSpam archived · refund heldReviewer checking answersWaiting on your approvalSession over · note writtenOne entry point for the workspace

Knowledge base

note
inbox
filing
pages

supportClaude Code

› answer 7 questions
  search the knowledge base
  ✓ 7 answers drafted
$ archive 2 spam
✓ archived
✕ refund reply held for you

reviewerCodex

› check 8 replies against policy
  1 suggestion: add the order link
✓ approved

developeropencode

› log 2 bug reports
✓ added to the tracker

skills6 picked from a library of 120·versions pinned

Seven steps, from the first trigger to the knowledge base.Watch one job go through a workspace.01 Trigger. It’s Monday at 9: the weekly social workflow starts on its schedule.02 Brief. The chief of staff reads last week’s notes and wins, and briefs the marketer.03 Draft. The marketer drafts the week’s posts for X and LinkedIn, live in Herdr.04 Guard. Posting straight to X is refused: posts go to approvals first, enforced outside the agent.05 Review. Codex checks the facts and the tone against the knowledge base.06 Approve. You approve the week’s posts in Slack, and they’re scheduled.07 Learn. The session ends with a note, so next week’s posts build on this week’s.

#social Slack

Schedule · Monday 09:00Weekly social posts

Chief of staffPulling last week’s wins for the posts.

Chief of staffSchedule 5 posts for this week?✓ ApprovedDecline

Chief of staffScheduled. Notes filed.

workspace · side-projectworkspace · personal

workspace · acmerules enforced outside the agent

Chief of staff

Claude Code · knows every project here

Waiting for workWeekly social workflow startedRead 6 notes · briefing marketerMarketer is draftingDirect post refused · queuedReviewer checking factsWaiting on your approvalSession over · note writtenOne entry point for the workspace

Knowledge base

note
inbox
filing
pages

marketeropencode

› draft this week’s posts
  5 posts · X and LinkedIn
  ✓ drafts ready
$ post now to X
✕ refused: posts need approval
✓ queued in approvals

reviewerCodex

› fact-check 5 posts
  1 date corrected
✓ approved

supportClaude Code

  idle · role from a template

skills6 picked from a library of 120·versions pinned

Seven steps, from the first trigger to the knowledge base.Watch one job go through a workspace.01 Ask. You message your workspace’s chief of staff from Slack.02 Brief. It reads the knowledge base and briefs the right agent.03 Build. Claude Code does the work in its own terminal, live in Herdr.04 Guard. A push to main is refused by a rule enforced outside the agent.05 Review. Codex reviews Claude’s pull request: a second provider checks the first.06 Approve. You approve the merge with one tap in Slack.07 Learn. The session ends with a note, filed into the knowledge base.

#acme-dev Slack

YouCan you fix the signup bug? Safari users can’t finish.

Chief of staffOn it. Briefing the developer.

Chief of staffApprove merging PR #128?✓ ApprovedDecline

Chief of staffMerged. Notes filed.

workspace · side-projectworkspace · personal

workspace · acmerules enforced outside the agent

Chief of staff

Claude Code · knows every project here

Waiting for a messageNew message in #acme-devRead 3 notes · briefing developerDeveloper is workingPush blocked · PR opened insteadReviewer checking PR #128Waiting on your approvalSession over · note writtenOne entry point for the workspace

Knowledge base

note
inbox
filing
pages

developerClaude Code

› fix signup on Safari
  edit src/signup/form.ts
  ✓ 48 tests pass
$ git push origin main
✕ refused: main needs review
✓ opened PR #128

reviewerCodex

› review PR #128
  2 files · 1 suggestion
✓ approved

marketeropencode

  idle · role from a template

skills6 picked from a library of 120·versions pinned

The opinions

Four opinions, decided for you.

You can rename or tune each one, but not remove it. That’s what makes it a framework.

A chief of staff in every workspace
Each business or area of your life is its own workspace, with its own agents, skills and knowledge. You talk to one chief of staff per workspace, from Slack or Telegram. It knows every project there, and nothing outside it.
The knowledge loop
Every session ends with a note. Notes land in an inbox and are filed into the knowledge base for you. Agents never edit it directly, so it stays something you can trust.
Scoped skills
Skills live in a library that’s never loaded into an agent. Each workspace picks and pins its own set, and each agent picks from that. Nothing leaks everywhere, and nothing changes under you.
```
 support · claude code
$ refund order 4417 £80
✕ held by the broker: over £50 needs you
$ email every customer
✕ denied: bulk email isn’t allowed here
$ post reply to review #212
✓ posted after your approval
```
the brokerspending limitspermission rulesGitHub rulesets
04
Guardrails outside the agent
An agent that can act can’t be stopped by asking nicely. Rules are written once and enforced where the agent can’t switch them off: the broker that holds refunds, posts and emails for your approval, spending limits, each workspace’s permissions, and GitHub for code.

Not another agent loop

Herdr is the engine. Wheems is the missing layer on top.

Chatting with one agent from Slack is useful on its own. Wheems is the set-up around it: a workspace for each part of your life, a chief of staff in each, agents from different providers, a knowledge base that keeps itself up to date, and rules the agents can’t switch off.

Aspect	Typical agent harnesses	Wheems
The agent	Their own agent loop calling a model	Claude Code, Codex and opencode, unchanged, each in its own terminal
Improvements	Arrive with the harness’s releases	Every Claude Code or Codex update reaches every agent
Seeing the work	Logs and chat replies	Every agent is live in Herdr, where you can step in
Scope	One instance per business	One install, many isolated workspaces
Set-up	Many choices left open	One way to do each thing
Cross-checking	One provider	Agents from different providers check each other

Getting started

From install to your first chat in Slack.

Install it once, connect Slack, create a workspace. Its chief of staff answers from your phone, and every job runs as a real agent session you can watch or take over.

Preview

$ npm install -g wheems
$ wheems setup
wheemsYour crew, ready for work.✓ Created ~/wheems
✓ Slack connected
$ wheems init acme
✓ Workspace acme, kept apart from the others
✓ Chief of staff on Claude Code, live in Herdr
$ wheems doctor
✓ Node.js  ✓ Herdr core  ✓ Claude Code  ✓ Slack  ✓ Service

Wheems is an early preview, and these commands may change between releases.

Helpers included.

Where it is, November 2026: version 0.0.3 is on npm, an early preview under Apache 2.0. Chatting with a chief of staff from Slack and a knowledge base it keeps up to date work today. Try it, but don’t rely on it yet: the build log says what got built each week, and why.

Or follow @mikejdeeming on X

Wheems: Your own little cloud of helpers.

Not just code. Any work you can describe.

Support inbox

Reviews

Social media

SEO and content

Bookkeeping

Code

Five layers, one install.

Any job, the same seven steps.

Four opinions, decided for you.

A chief of staff in every workspace

The knowledge loop

Scoped skills

Guardrails outside the agent

Herdr is the engine. Wheems is the missing layer on top.

From install to your first chat in Slack.

Helpers included.