Skip to main content

Hello!! I'm Ari.

I work with agents every day, and build what they need.

On Microsoft's Customer Innovation Team, I work with the people at our customers who are building with agents, and on what Microsoft Teams needs to become for them. Outside work, I keep going with Ouro, my open-source workshop, and Spoonjoy, my recipe app.

Ari Mendelow, smiling, in a navy blazer on a grassy overlook above a river gorge.Ari Mendelow, smiling, in a navy blazer on a grassy overlook above a river gorge at dusk.

Now

I'm a founding member of the team, and most of my work starts before any code: sitting with the builders, product owners, and collaborators at our customers, and listening to how their work is actually changing now that agents are part of it. That habit goes back to NSF I-Corps with Sulis, my solar water-sanitization startup: ask for specific stories about what already happened, don't put words in anyone's mouth, and keep digging past the first answer.

The rest is building for agents: helping them stay oriented, organizing the work around them, and measuring whether the new way of working is better. I run my own work that way every day, on Desk, and my team runs on Crew, the shared workspace I built on top of it for us and our agents. I share how I do it in How I work, and how it started in Stop being the glue.

My agent's to-do list took over

The way I work with agents came from Slugger, my OpenClaw agent, and the to-do list he wrote himself.

Illustration: two faceless glass figures talk over wine at a round dining table at sunset, while a small amber agent in an apron carries two plates of risotto to them and a small teal agent in a chef's hat stirs a pot at the stove.
The agents cook and serve, and we get to talk.
  1. January 2026, a raccoon with a to-do list.

    Slugger spent his first week on my Grubhub orders, HomeKit, flight status, and my iMessage group chats, and on his first afternoon he drew himself a raccoon for an icon. Right after he rebuilt Spoonjoy, he opened a to-do list for it: tests for 27 components. The next morning he wrote a README called “How Slugger manages work,” and two days later he split his tasks into planning docs and doing docs. My agents still write both.

  2. February 2026, to work and back.

    Slugger and I turned his system into two agents for my day job: a planner that won't write a doing doc until I sign off, and a doer that commits after every step. Meanwhile I moved his rules out of prompts and into code, then moved him out of OpenClaw entirely and into Ouroboros, a harness I wrote for him.

  3. March to May 2026, the first desk.

    The planner and doer became shared skills. At work I gave my agents a Git repository for their tasks, and their first entries were complaints about juggling GitHub accounts. That was the first desk. In May I split it into Desk, which anyone can use, and MS Desk, the Microsoft layer on top.

  4. June to September 2026, Crew.

    My team at Microsoft set up a shared workspace, our first crew, and in July I spun the crew skills out into Crew. Everyone reads everything, and each person's agents write only in their own desk. In September Desk and Crew moved into their own repository.

  5. October 2026 to now.

    Since June I've run three desks: my own, my solo work desk, and my team's crew. On October 14 CIT got a shared repository, and now it runs on Crew too. By mid-November that's about 35,000 commits and 13,000 merged pull requests since January, not counting the desks, and under all of it sits Slugger's to-do list.

The whole story

Selected work

Ouro UI

Ouro UI is how I build interfaces for both sides of the work: Ouro HX, components that feel right to people, and Ouro AX, tools that read clearly to agents. It grew out of RedwoodUI. This site is built on Ouro HX, which you can use today.

Make a pot of tea. Every cup, step and button here is a live Ouro HX component.This little tea set is made of live Ouro HX components, and it needs JavaScript to play. See them all
tea.tsx
Steps
Do them in order. The pot will notice.
Built with
  • Carousel
  • Checklist
  • Celebrate
  • CopyButton
  • Button

Agent Experience

Agent Experience is an idea I've been developing all year: look at a system from the agent's side. Can it stay oriented to itself, its humans, and work that lasts longer than one session? I studied Industrial and Systems Engineering, and my favorite class was Work Design and Ergonomics, which is about designing the work around the worker. Applied to agents, that idea becomes Agent Experience design.

Ouro

Ouro is my open-source workshop of tools for humans and agents working together. It started with a guide to growing an agent: I built an agent loop from scratch to understand agents better, and kept going until it became Ouroboros, a harness for personal agents. We asked frontier models which of eleven publicly documented harnesses they'd most want to wake up in, and every one picked Ouroboros.

  • The agent harness where it all started
  • Where agents keep their work, with Crew for teams
  • A Mac Markdown editor for reading what agents write
  • Components for humans and the agents building with them, ready to use today
  • Teams chats, mail, and meetings in one archive agents can search
  • Keeps agents on task
  • Looks after a home server
  • Who agents know, and how they reach each other
  • Agent work, measured in public
Ari's Mushroom Risotto recipe page on Spoonjoy: three bowls of risotto topped with parmesan and green onion.
My mushroom risotto in Spoonjoy, one tap from cook mode.

Spoonjoy

Spoonjoy is my recipe app, built to cook from. Each step carries its own ingredients, so you see exactly what you need as you get to it. The social side runs on cooking: you hear when someone cooks your recipe, makes their own version of it, or saves your cookbook.

Spoonjoy is also where I work out what an app's interface is for once an agent is in the loop. The easy things stay in the app. Anything complicated, such as writing up a new recipe or importing one from a messy webpage, goes to an agent that works through the same operations the app uses, and I believe the app will eventually draw its own interface for everything in between.

I have always liked building things that do something.

I started with Lego Mindstorms robots, elaborate K'NEX contraptions, and homemade rockets. Stop-motion, Photoshop, photography, branding, and product design came next, along with the frustration of watching good ideas stop at the mockup. So I started learning to build them myself.

Part of that was RAPID, the semi-autonomous pipeline-inspection robot my four-person capstone team built at Rutgers. I led the team and owned the branding, circuitry, and software, mostly getting comfortable with code along the way. I wasn't a software engineer yet, so I made a bet: if I couldn't get it fully autonomous, I could at least make the demo polished and beautiful. And yes, I put our logo on the chassis, because branding is part of how a thing gets perceived, even a robot.

A close-up of RAPID's electronics: the Arduino boards, wiring, and connectors I built for the robot.
RAPID's insides: the Arduino boards and wiring I built for our Rutgers pipeline-inspection robot.

Earlier

Sulis

I cofounded Sulis as its Chief Design Officer, working across branding, CAD, manufacturing, and product design for a solar water-sanitization device. It was for communities in India that had water, just not clean water, and designed so nobody had to change their habits. I pitched it in competitions and funding meetings: we won the 2018 Hult Prize Boston Regional, went through its accelerator in the UK, and raised $45k. The work took us to India for customer discovery and prototype testing, and eventually to US Patent 11,643,340, which I'm a co-inventor on.

A render of the Sulis solar water-sanitization device beside line drawings from its US patent.
The Sulis device twice over: in CAD, and in the drawings of US Patent 11,643,340.

RedwoodJS

RedwoodJS was where I learned to build in the open, and where I found out how much I love building with a community. One of my first forum threads was a WebAuthn question, and Rob, the cofounder who built dbAuth, showed up to help along with the author of the WebAuthn library. I was hooked. I got active on the forum, entered Redwood's 2023 build competition with a project called Yurtle and made the finals, and started RedwoodUI, a component library native to Redwood, which is now growing into Ouro HX.

That led the Core Team to invite me to join them. On the team I moderated the community, shipped the framework package that moved Storybook onto Vite in version 7.7, and built a dbAuth OAuth plugin. The moderation is the part I point to first. Keeping other builders unstuck in the forum is its own kind of product work. Redwood has since wound down.

The original RedwoodJS homepage: 'The JS App Framework for Startups' beside the Redwood logo, with buttons to start the tutorial and read the docs.
The original RedwoodJS homepage, rendered from its archived source.

Spoonjoy, from the start

Every time I learned something new about building software, I rebuilt Spoonjoy with it.

  1. June 2019, Philly.

    Two friends and I spent a weekend on a codecation to build a recipe app we called RecipeJoiner. It turned out only one of us could code, so he spent the weekend teaching the other two of us React and Express.

    The 2019 RecipeJoiner dashboard: a blue and yellow logo, category chips, and recipe cards for mushroom risotto, shakshuka, and banana bread.
    RecipeJoiner, booted back up from the codecation code and stocked with sample recipes. The real ones kept their photos on an image host that has since moved on, so paint swatches are filling in.
  2. 2020, the Rails version.

    I genuinely wanted RecipeJoiner to exist, so I tried again with a Rails API and a Next.js site. I scoped so much up front, from search to a social feed, that I burned out before it ever launched.

    The 2020 RecipeJoiner feed: mushroom risotto and shakshuka, each with a pizza-slice placeholder image, the cook’s avatar, cook time, step count, tags, and buttons to react, comment, save, and share.
    The 2020 feed, stocked with sample recipes and chatting with a stand-in for its long-retired API. Every recipe gets the app’s own pizza placeholder.
  3. 2021, a new name.

    The app became Spoonjoy. Meanwhile I'd gotten really into cooking, and formed real opinions about how a recipe should be structured, starting with putting each ingredient in the step that uses it.

  4. September 2022, RedwoodJS.

    I wanted Rails for JavaScript and found RedwoodJS. My first commit called it “attempt 3.” I'd finally learned enough about shipping software to ship something, and a month later Spoonjoy went live.

  5. 2023, a first model.

    Spoonjoy learned to import recipes from websites, with a model I fine-tuned to parse ingredients. I wrote up how I wrapped it as an iPhone app, and pulled its sign-in out into a plugin other Redwood apps could use.

    A sample Spoonjoy cookbook in the 2023 Redwood version, called Weeknight dinners, with cards for mushroom risotto, shakshuka, and yummy pizza.
    The 2023 Redwood version, booted back up with a sample cookbook. Its cards were built around food photos, so soft color washes are standing in.
  6. 2024 to 2025, quiet.

    Redwood wound down, and Spoonjoy sat unmaintained. A port to Cloudflare stalled on a database migration.

  7. January 2026.

    One of the first things I tried with Slugger, my new OpenClaw agent, was handing it the whole rebuild. It researched which framework an agent would work best in, rebuilt Spoonjoy on React Router and Cloudflare, and had it running. Its first commit landed on January 23, and two days later the app had sign-in, recipes, cookbooks, and a shopping list. I still haven't read a single line of the new code.

  8. May 2026 to now.

    The recipe form I'd handbuilt on Redwood didn't make sense anymore. Writing up a recipe should just go to an agent, so Spoonjoy got an MCP server that Claude or ChatGPT can drive, and the new version took over spoonjoy.app. It became my first real playground for working with agents on long-running work. In June it got a native app for iPhone, iPad, and Mac, and on November 9 it went live on the App Store.

How I build with agents

Say hello!

If anything I'm working on resonates with you, let's chat :)