A Snapshot of How I'm Using AI in February 2026

Avi Press | February 17, 2026

This post is a follow-up to my January snapshot. My AI stack is continuing to change a lot, but OpenClaw is very much at the center of it all.

This month, the biggest shift is that even more real work is getting done. Recurring tasks are increasingly being moved into dedicated subagents and an intentionally very lightweight orchestration system.

What's changed since January

OpenClaw has its own accounts for more autonomy with a blast radius.

I gave OpenClaw its own:

  • email address on my personal domain
  • It's own personal gmail, mainly for Google Drive
  • A phone number via esim, which allowed me to move my main chat from Telegram into WhatsApp (for the encryption).
  • GitHub account
  • A strictly protected service account in Scarf's Google Workspace.

This is helpful to separate the work that OpenClaw does from my own, and lets me grant fine-grained access to resources more natively to whatever platform its using.

I now run a small set of focused agents instead of one overloaded chat

Instead of a single long thread trying to handle everything, I have specialized agents for recurring workflows (engineering tasks, reporting, meeting follow-up, lead ops, writing support).

Each one has a narrow scope, a schedule that it runs on, and a lightweight orchestration system that I am building on top of org-mode (more on that below). Some of my subagents run daily, others run every 30 minutes, especially the ones writing code.

Org2 as the orchestration layer

I've long wanted to build an org-mode successor, and now it's finally happening with the help of OpenClaw.

Each long-standing subagent now has a dedicated org2 file in Dropbox. Each has its heartbeat instructions in its org2 file, and logs its work, summary status, and blockers. That way, I can easily monitor whats happening from my editor and intervene asyncronously when needed, without getting in the way of the normal chat flow.

I am dogfooding org2 for myself as I do this, and migrating myself off of emacs (finally) and into the VScode ecosystem.

Org2 is still not ready for prime-time, but it is already supporting most of my day to day org-mode usage!

Meeting follow-ups are much more automated now

A lot of value has come from kicking off meeting follow up items more automatically:

  • Meetings are transcribed with Hyprnote.
  • Every hour, MeetingBot will SSH into my laptop, check for new meeting summaries.
  • Any product feedback we get triggers a new Linear ticket to be made, checking for duplicates first.
  • Any other follow up task for me is logged into my daily org mode notes, so I can track and get reminders on all of my devices.

This has been hugely helpful at a time where I am in lots of meetings.

An always-on data analyst in Slack

OpenClaw in our #analytics channel can easily answer any questions I have, and is even now handling our customer-facing reports.

A tedious spreadsheet tasks is now fully automated

Scarf offers lead gen services as an add-on to our platform. That has historically required a human to move leads from an internal spreadsheet to an external one, with different fields. OpenClaw has automated this fully!

Other changes

  • Codex 5.3 for basically everything.
  • More personality via a much more robust SOUL.md than I had before.
  • Less voice notes and more pictures, mostly because voice notes are slow (with my current setup)
  • QMD plugin for the memory layer.

Open Problems

  • Memory is still not reliable enough.
  • Real time voice chat.

© Avi Press 2026

Twitter GitHub LinkedIn Bluesky