@reedchan7@RLanceMartin Let’s say you want a new feature. You hat would be the usually workflow? Let Claude create 6 or more phases with reviews and go through through each phase and review one by one? Or build a loop that does slot that?
The new iOS share sheet in @obsdmd lets you save X posts, YouTube transcripts, and content from other apps. Everything is converted to durable Markdown files.
Try it in Obsidian 1.13 (beta)
We never had more npm downloads than this week on @openclaw - comined with Docker, GitHub, company-internal deployments and the numerous forks, real number is more in the 10-20 million downloads/week.
Codex now has more than 5M weekly active users.
But the bigger story is what people are using it for: not just writing code, but getting more work done across research, analysis, content, and operations.
Our new report on how Codex is becoming a productivity tool for knowledge work: https://t.co/XZMPR9cEge
@mvanhorn@openclaw@NousResearch In my case I just want to sync login from my Google Chrome to playwright on the same machine. Or are there easier/better solutions for my case?
@OpenAI I want codex and ChatGPT have a baby. Don’t keep them separate, join them to one united product. Also give it more capabilities in the direction of caseclaw and Gemini spark. Have us communicate with it via a master/top-level-agent similar to Claude dispatch.
Your Mac can hold down the fort while you work from your phone.
Enable remote connection in the Codex desktop app, then turn on “Keep this Mac awake.”
When your Mac is powered on and plugged in, Codex can keep running there while you work from the ChatGPT mobile app.
People freaking out over my AI spend. What nobody sees: Part of what excites me so much about working on OpenClaw is that I'm trying to answer the question:
How would we build software in the future if tokens don't matter?
We constant run ~100 codex in the cloud, reviewing every PR, every issue. If a fix on main lands, @clawsweeper will eventually find that 6 month old issue and close it with an exact reference.
We run codex on every commit to review for security issues (as it's far too easy to miss).
We run codex to de-duplicate issues and find clusters and send reports for the most pressing issues.
We have agents that can recreate complex setups, spin up ephemeral https://t.co/Q1NRXLemEy machines, log into e.g. Telegram, make a video and post before/after fix on the PR.
There's codex that watch new issues and - if it fits our documented vision well, automatically create a PR of it. (that then another codex reviews)
We have codex running that scans comments for spam and blocks people.
We have codex instances running that verify performance benchmarks and report regressions into Discord.
We have agents that listen on our meetings and proactively start work, e.g. create PRs when we discuss new features while we discuss them.
We build https://t.co/bmA1XnoB7P to split all our projects into functional units to review and find bugs and regresssions.
We do the same split for security with Vercel's deepsec and Codex Security to find regressions and vulnerabilities.
All that automation allows us to run this project extremely lean.
We've been working for nearly a year to launch this new Community site and review system. I'm very excited about this first version but there are many more improvements to come.
I've tried to be exhaustive with the blog post, FAQs, and next steps on our roadmap, but I am sure I forgot some things, so feel free to ask!
This has been an incredibly challenging project for a number of reasons. We're only seven people but we have thousands of plugin developers and millions of users. There are many competing priorities to balance.
We wanted to make sure the new system would be easy to adopt, backwards compatible, and not completely break people's workflows, while still being a major improvement over the old approach, and allow us to gradually continue enhancing security and discoverability of plugins.
Consider it a work in progress. We're listening to everyone's ideas and gripes, and will keep iterating :)