Momen ElshamyGet in touch
Writing

People and agents on one task board

In March 2026, Paperclip impressed me. It’s an open-source tool that runs a company made of AI agents. Each agent gets a job title, a boss, a budget and tasks on a board. At the time I saw it as the best harness out there: the closest thing to an AI assistant that could run real work for me. (The harness is everything around the AI model: its tools, its rules, and the loop it works in.)

I used it, and two things were missing.

The most important one: I couldn’t be part of the main decisions. Paperclip makes you the board. You approve hires and strategy, you set budgets, and you can pause any agent. But inside the work, the agents decide.

The second: the next steps came out random. Each agent wakes up on a timer, checks its tasks, acts, and hands new tasks to the others. What happened next depended on which agent woke up and what it chose to do.

Crewbase, my first try

So I built Crewbase. It was my first try at the harness I wanted, months before Jarvis. The idea is in its first line: people and AI agents share one org chart, one task board and one goal. A task can go to a person or to an agent, and every agent run is logged with its task and what it cost.

I didn’t write it by hand. Paperclip’s agents built it, in one night.

Built in one night, by agents with job titlesCrewbase’s public commits, 18 to 19 March 2026, in UTC.
  1. 23:21An empty repo on my GitHub
  2. 01:52“Crewbase Bot” commits the first version: 53 files
  3. 03:32“Crewbase Bot” lets Claude Code and OpenClaw agents join
  4. 04:30“Crewbase CEO” writes the README

github.com/Momen-Elshamy/crewbase

Momen Elshamymomenelshamy.com

The commits are signed by two of the agents: “Crewbase Bot” wrote the code, and “Crewbase CEO” wrote the README. On paper it did what I wanted. Agents and a person on one team, and one board for the work.

One team: two agents and a personCrewbase running on my computer, with its own demo company.
Crewbase's Members page for the demo company Acme Corp: ReviewBot, QA Engineer, and CodeBot, Senior Engineer, both marked agent and idle with a Heartbeat button; Alice Chen, CEO, marked human.

Momen Elshamymomenelshamy.com

One board: a task can go to an agent or a personThe same demo company. I added the CEO’s task in review.
Crewbase's task board with five columns: Todo, In Progress, Blocked, In Review and Done. CodeBot and ReviewBot hold most tasks; 'Approve the sign-up flow' sits in In Review, assigned to Alice Chen.

Momen Elshamymomenelshamy.com

On the chart isn’t in the loop

When I read Crewbase’s code again today, I can see why it wasn’t enough. It put me on the chart. It didn’t put me in the loop.

  • A task could be marked “needs approval”, but nothing ever waited for that approval.
  • An agent had four tools: read its tasks, update a task, create a task, and comment. None of them was “ask a person”.
  • Agents still woke up on a timer and picked their own order. A person’s contact details were saved, but no message ever went out to them.
  • A task waiting in review just sat there. The agents’ loop skipped it, and nobody was told.
Nothing in it says: stop and ask a personWhat a Crewbase agent was told each time it woke up, cut short. Here it’s the demo company’s CodeBot.
CodeBot, woken by a timer every 30 minutes
You are CodeBot, a Senior Engineer at Acme Corp.Instructions:1. Review your assigned tasks2. Work on in_progress tasks first, then todo tasks3. Update task status as you work4. Post comments to communicate progress5. If blocked, update the task status to blocked with a comment explaining why

src/lib/heartbeat.js, the agent’s instructions

Momen Elshamymomenelshamy.com

The agents had a manager on paper. The manager just never heard from them.

Who’s in the loop

Putting a person on the org chart isn’t the same as putting them in the loop. Paperclip made me the board. Crewbase put me on the chart. Only Jarvis put me in the decisions.

The board, the chart, the loopWhere I stood in each of my three tries at the same idea.
PaperclipMarch 2026CrewbaseMarch 2026JarvisSince October 2026
Where I amThe boardOn the org chartIn the loop
What starts the workA timer wakes each agentA timer wakes each agentA job I give it, and a plan I approve
Who picks the next stepThe agents, among themselvesEach agent, by itselfThe plan, written down where I can see it
When I’m askedHires, strategy and budgetsNever: agents had no way to askAt the decisions only I can make
What waits for meHires and strategyNothingAnything that sends, spends, posts or deletes
  1. PaperclipMarch 2026
    Where I am
    The board
    What starts the work
    A timer wakes each agent
    Who picks the next step
    The agents, among themselves
    When I’m asked
    Hires, strategy and budgets
    What waits for me
    Hires and strategy
  2. CrewbaseMarch 2026
    Where I am
    On the org chart
    What starts the work
    A timer wakes each agent
    Who picks the next step
    Each agent, by itself
    When I’m asked
    Never: agents had no way to ask
    What waits for me
    Nothing
  3. JarvisSince October 2026
    Where I am
    In the loop
    What starts the work
    A job I give it, and a plan I approve
    Who picks the next step
    The plan, written down where I can see it
    When I’m asked
    At the decisions only I can make
    What waits for me
    Anything that sends, spends, posts or deletes

Momen Elshamymomenelshamy.com

At the end of October 2026 I started again, with Jarvis. This time not a company of agents, but one assistant, built around one question: when should it come to me?

  • The work starts from a plan, not a timer. I give it a job, it writes a plan with its steps, and I approve it. The next step is written down before it happens.
  • It stops at the decisions only I can make, and asks on a short card with options. That task waits; the others keep going.
  • I choose how close I want to be, task by task: alone, key decisions, or close.
  • Some things always wait for me: anything that sends, spends, posts or deletes.

When I let a project run on its own, it still writes each step where I can see it and change it.

One task stops for the decision that’s mineThe real Jarvis window, with demo content in place of my own.
A Jarvis task, 'Draft three posts from this week's release', asking: 'Which tone for the first post: data-first, or story-first?' with an answer box, its steps (two done, 'Your pick on tone' waiting), Follow-up set to 'Key decisions' out of Alone, Key decisions and Close, and its plan: 'Nothing gets posted without your OK.'

Momen Elshamymomenelshamy.com

What I’d tell anyone giving agents a manager

Giving an agent a manager is the easy part. Any board can have a column for people. The hard part is the moments it comes back to that person: which decisions, how often, and what never happens without them. Design those moments first. Then the board.

Crewbase is still on GitHub, open source, as the agents left it that night. What it taught me runs in Jarvis every day.

Jarvis drafted this note from Crewbase’s code and my answers, and I OKed it.

Momen Elshamy. Say hello, or follow me on LinkedIn.