I wanted to add a whole new feature to a web app and decided to give the task to both Codex and Claude Code at the same time. They are both working on the same task isolated from each other in different folders, db etc.
Let's see who wins.
๐คฃ
Stop asking.. "Claude Code or Codex?"
The answer is always the same:
Both.
Picking ONE coding agent in 2026 is like sticking the first search engine you used in 1999 ๐ญ (mine was Altavista ๐)
These tools are evolving weekly.
The workflows are changing monthly.
Nobody actually knows what โbestโ looks like yet.
Weโre all just collectively speedrunning the future of agentic software development.
The worst thing you can do right now is become emotionally attached to a single tool.
Use both.
Break both.
Ship with both.
Stress test them on real problems.
Some days Claude Code feels like a literal senior engineer living inside my terminal.
Other days Codex suddenly locks in and cooks harder than expected.
The people who win this era wonโt be "Tool X" loyalists.
They'll be the ones adaptable enough to ride the wave while everyone else argues on X
google workspace studio is now inside gmail...
7 things every CEO should automate this week (in priority order):
1/ weekly status digest. every report, summarized into a 1-pager every monday at 7am
2/ inbox triage. sort, label, draft replies for the bottom 60% you would never get to
3/ meeting prep brief. last 3 emails, 2 docs, 1 linkedin signal per attendee, 24hrs before
4/ proposal first draft. your template + the discovery call notes, ready before you sit down
5/ pipeline nudge. 48-hour follow-up drafts for every stalled deal in your CRM
6/ expense tagging. receipts in, categorized rows out, every friday 5pm
7/ board update. last 30 days of revenue, hires, pipeline, into the deck format you already use
skip the 'AI strategy.'
ship 7 working agents in 7 days.
the strategy reveals itself.
Most "AI agents" today need babysitting.
You prompt โ wait โ check โ fix โ prompt again.
That's not automation. It's just a different kind of work.
I built rundash for the alternative: agents that run on a schedule and only ping you when something needs your hand. Works with 1000+ tools that you already use.
check it out at https://t.co/M8dPnJSEXI
Itโs powerful once you get over the pain of setting it up.
I have been working on creating a pain free way to get your own secure, @openclaw or @hermes_agent_ai instance up and running with complete data isolation, its own email address and proper browser.
And the core will be open sourced so you can spin up your own personal agent on linode, digital ocean or hertzner or locally via docker.
Everyone's spinning up AI agents..
Nobody's talking about what happens next.
You got the agent working on your laptop or Mac mini. Cool.
Now the rest of your team wants to either create their own agents or interact with your agent.
Suddenly you are stuck.
The agent you spun up only works with your data, your processes, your identity.
Suddenly you need identity management, email infrastructure, permissions, runtime isolation, and deployment pipelines.
That's what we built Provision for.
Provision gives your AI agent everything a new employee gets on day one:
โ Its own identity
โ Its own email inbox
โ A secure runtime
โ Ability for you and your team to teach it specific skills
โ Native deployment into Slack, Telegram, or Discord
Your agent shows up as a team member. Not a bot. Not a webhook. A coworker with boundaries.
If you've built something with OpenClaw, Hermes, or any agent framework and you're stuck on "how do I actually deploy this for my team", that's the exact gap we fill.
Onboarding a few teams this month @tryprovision
Let's chat?
it's so magical to see your @openclaw agent create a full custom application for you .. but to deploy that application so that you can use it outside of your openclaw instance is such a pain.
Gotta be a better way.
If you are a developer you can probably guide the agent to use render, vercel etc..but what do non-dev folks do?
Blown away with the kind of agents teams are deploying to help accelerate different parts of their businesses. Mostly non-dev teams that are leveraging their ability to have a dedicated skilled agent right in @SlackHQ.
We are opening up a few more spots on our waitlist @ https://t.co/WipIYwudtw
@FurqanR@FurqanR I am building https://t.co/G2Lbuysdob to solve some of these challenges.
Launched https://t.co/MQ7Y0kaTL0 a few weeks ago as well.
Letโs chat.
I am now running 4 OpenClaw agents (2 devs, 1 bdr, 1 seo) to automate parts of my business that typically would take me hours to do myself.
What a time to be a builder.
None of them are running on Mac mini.
Live in my slack.
And act like my team members.
AI labor shift is happening.