title: @timourxyz: I was about to get my whole team to set this up. Now I'm telling them to wait. A...
author: timourxyz
content_type: twitter_article
published: 2026-02-15T18:47:51+00:00
source_url: https://x.com/timourxyz/status/2023107002243707079
word_count: 1768
I was about to get my whole team to set this up. Now I'm telling them to wait. At least until they r
I was about to get my whole team to set this up. Now I'm telling them to wait. At least until they read this.
I'm 15 days into an experiment of working fully agent-first.
What I mean by agent-first work: for any task that could possibly be done by my agent (~95% of knowledge work tasks), I set things up so the agent can do it, assuming that if it can do it once, it can automate it for the future.
My personal AI agent (I call it R2, full name R2-D2) is built mainly with Claude Code + Obsidian. It knows my to-dos from Todoist, reads/drafts my emails, scans my team chats, pulls in Granola meeting notes, analyzes team context from Notion, preps me for calls, drafts content, and has a weekly sweep to find ideas to improve itself that we discuss on Sundays.
Two weeks ago, I started with a full "R2 take the wheel" mindset. In week 1, it felt exhilarating, and tbh I haven't enjoyed work so much in a long time. Now, at the end of week 2, I'm not so sure. I think I went a little too far off the deep end, and it affected my work and mental health.
In week 3, I'm going to find a happy middle. I think we all need a nuanced approach to how we deal with these upgrades.
TLDR / key takeaways
If you're short on time, here are the five things I learned. If you're building with agents or planning to, bookmark this. You can also paste the guardrails section at the bottom directly to your agent as instructions.
The good:
Agent-first work genuinely can fully automate a lot of my job (maybe ~18% so far) and could likely increase to ~30% in the next couple of months. The gains are real.
The addictive:
It has the same dopamine mechanics as a video game. Variable reward, "just one more thing," eyes glued to screen. You will spend a lot of time early-on improving the system compared to doing your actual work if you're not careful.
The learned helplessness:
You start wanting to delegate everything, and start thinking "why can't my agent just do that" for every task, even basic things.
Just one more prompt:
The "just one more thing" energy spills into ALL your work and eventually your life. Before every break, you think, "What can I make my agent do during that time?" It's stressful. Deep focus becomes harder. Your whole day turns into a frantic race of micro-tasks.
The fix:
treat agent time like you'd treat social media. Give the self-improvement part a time-boxed container. Learn what it's good for and do not use it for what it's not good for (sounds obvious, but it's quite hard).
Okay, the full version.
What R2 actually does
My job is building Edge City. It's a mix of partnerships, comms, strategy, team coordination, content. Lots of context flying around in lots of places.
The setup is pretty simple. I use Claude Code (on a Max subscription, so I'm not burning API tokens) as the agent runtime, and Obsidian as the knowledge base where everything lives. Notes, drafts, project pages, daily logs. Claude Code reads and writes to the vault, connects to my email, Telegram, Notion, calendar through MCP servers.
I started with OpenClaw, but honestly ended up preferring Claude Code for this (I use OpenClaw for other fun autonomous experiments). The whole thing is evolving fast, so if people are curious about the actual setup I can do a follow-up post, but for now the interesting part is what happens when you use it.
R2 sits on top of everything via MCP. Every morning, it scans my email, team group chats, and meeting notes from the day before. It gives me a summary of what shifted since the last update. It's actually remarkably good at this, and I notice that it probably only misses 5% of the context of everything that's happening. It logs it all in Obsidian.
When I need to give feedback on a draft, it pulls in the project goals and the draft and gives me structured notes in about a minute. Things I'd normally forget about, like that email from three days ago I never responded to, get surfaced.
That part is genuinely great. I can see large chunks of my job being reliably automated; could probably get to ~30% with a few more weeks of refinement. The productivity gains are real, and I don't want to undersell them.
The dopamine problem
So here's where it gets tricky. And this is the part I really want people to hear, because I think it's going to hit a lot of people once these tools become more accessible.
Working with an agent has the same eyes-glued-to-screen dopamine feeling I remember from being a kid and playing Age of Empires II, looking up to realize four hours had passed. But it's worse, because it's "productive", so it taps into the part of you that wants to be good at your job.
You give it a task. Sometimes it nails it, and you get this rush. Sometimes it fumbles, and you tweak and try again. Sometimes it surprises you with something you didn't ask for. You have a bunch of different processes running at once, so by the time you set another one going, one of the earlier ones is done , and you could just prompt it to get it doing more. They also have the same variable reward mechanics as video games and slot machines.
The first few days, I told myself I was being productive when I was tinkering on "improving the system." And some of it was. But in retrospect, a lot of it was just busywork. Tweaking prompts, testing edge cases, seeing if R2 could handle one more thing. I was spending more time building the agent than doing the things the agent was supposed to help me with.
If you've ever lost a Saturday tweaking your Notion setup instead of doing the things Notion was supposed to organize, you know what I mean. This is that, except turbocharged, because the agent talks back. Every interaction feels like progress.
The learned helplessness thing
Something subtler happens after a few days. Once you've watched the agent do something in a minute that would've taken you an hour, your relationship to your own to-do list starts to shift. Every task, there's this tiny pull: "couldn't R2 just do this?"
I caught myself multiple times thinking, "Let me just set up R2 to handle this," about things that would've taken me 10 minutes to do manually, but 25 minutes to set up as an agent task. The math doesn't math, but the pull is there every time.
And then the really insidious part: "just one more thing" starts bleeding into all your work. Your day becomes this frantic race of pushing small things forward, getting a little hit each time. Before going for a lunch break, you wrack your brain thinking about something chunky that the agent can do while you're gone.
I've been doing knowledge work for ~15 years and I know what productive days feel like. The agent-first days felt productive in the moment. But when I looked at what actually shipped at the end of each week, it was thin.
What I'm changing for week three
I'm keeping R2. It's genuinely useful and I'm going to keep building it. But I'm getting back in the driver's seat. Here's what's working:
Time-box the tinkering. Agent improvement, prompt tweaking, "let me see if R2 can do this" exploration. All of that gets one hour in the after. In the morning, I do my actual work, and I use Claude the old-fashioned way: I decide what needs to get done, I forage for the context, I put it into a Claude chat, and workshop the answer. Same discipline people had to learn with email, Slack, social media. The tool gets a container.
Keep a "what shipped" log. End of each day, I write down what actually got done. What shipped. Not what R2 attempted. Not what prompts I refined. This is the reality check.
Use a regular LLM chat for thinking. I had stopped using Claude chat entirely, doing everything through the agent. Bad move. Thinking through hard problems, messy creative stuff, exploring ideas you don't have clear instructions for yet. That's better in a conversation where you're loading the context and making the decisions. Agent for execution. Chat for thinking.
Ask: "is this an R2-shaped problem?" Before every delegation, honestly ask yourself: could I just do this in 10 minutes? The setup cost of agent delegation is real. Save it for the things where pulling context from five different sources actually saves real time. Tell your agent to help you. This is key, and one of the big bonuses of working with an agentic system. You can just ask your version of R2 to check in with you about whether it's something you want to do together, or would prefer to just do yourself.
Watch the spillover. This is the one I think matters most. If you notice your whole day becoming a series of micro-tasks with little dopamine hits, that's the signal. Step away from the terminal. Go for a walk. Do an hour of focused work on one thing with your phone off.
Why I'm sharing this
Everyone is going to have one of these soon. Someone will make it normie-accessible, maybe in 3 months, maybe 6. And when that happens, a lot of people are going to go through exactly what I went through. The rush, the magic, the "holy shit it just did my job" feeling. Followed by two weeks of working longer hours with less to show for it.
I think the people who get the most out of this technology will be the ones who figure out the guardrails early. Before the guardrails feel necessary. There's also just the reality that honestly it could get way better very soon, especially with full context and better memory.
Fwiw, you can paste the "what I'm changing" section above directly into your agent's instructions. I've done that with R2 and it actually helps. Having the agent itself remind you to check your shipped log or time-box your tinkering is a nice bit of meta.
Going into week three. Eyes open, hands (slightly more) on the wheel.
With love,
Timour
R2, me, and OpenClaws
Posted: 2026-02-15T18:47:51.000Z
Engagement: 85 likes, 8 retweets, 10 replies