@foundsmoney Note that multiple security scanners have labeled https://t.co/C4eFVqyNlu as phishing (low trust score, blacklist hits), and the project itself says rewards stay locked and it is not affiliated with X.
@yucheng@tuttihq More specific The number that stands out is 1,431 people actually posting, not just signing up. 61k posts across 46 campaigns plus 8.6M effective impressions is a lot of output for that cohort. Curious how many of those 1,431 stay active in October.
@yucheng@tuttihq Creator-money angle Top single payout of $2,653 and one person already at $11k cumulative is the part brands and creators will both notice. Global fanbase across 189 countries with only 25% US is broader than I expected.
The useful part of Raven 0.2 isn't "another multi-agent framework." It's putting Claude Code, Codex, and specialist agents on one task graph with shared memory.
Raven 0.2.0 — The Harness of Harnesses, built for RSI. 🐦⬛
One harness can't be best at everything. Raven combines its own specialist harnesses (Research, Code, Design, Oncall) with the agents you already use (Claude Code, Codex and more) into one team.
And it's built for RSI, and not just at the skill level. The whole harness can be rewritten by AI: prompts, policies, strategy code, playbooks. Every sub-harness, including the orchestration layer itself, is its own instance that can be improved.
With Raven you can:
1. Orchestrate many agents as one team. Raven's sub-harnesses and external agents work in one task graph with shared memory across sub-agents, powered by leading orchestration (0.963 Node F1 on the Multi-Agent Orchestration Benchmark).
2. Run long, complex tasks. Oncall and proactive execution keep work going for days, from scientific research loops to shipping a full Godot game.
3. Build vertical agents with RSI. Use Raven's RSI to develop and refine an agent for your domain, and we'll optimize it with you. Experimental for now; reach out to the Raven team(Discord:https://t.co/jRrci3hVL5).
More in the video and slides below. Open source, Apache-2.0.
https://t.co/2GEA4Nmig0 (lots of work made with Raven lives there, and much of this launch's material was made with Raven too)
If the orchestration layer can rewrite itself, the product question stops being "which agent is best" and becomes "who audits the harness that is rewriting the harness."
Raven 0.2.0 — The Harness of Harnesses, built for RSI. 🐦⬛
One harness can't be best at everything. Raven combines its own specialist harnesses (Research, Code, Design, Oncall) with the agents you already use (Claude Code, Codex and more) into one team.
And it's built for RSI, and not just at the skill level. The whole harness can be rewritten by AI: prompts, policies, strategy code, playbooks. Every sub-harness, including the orchestration layer itself, is its own instance that can be improved.
With Raven you can:
1. Orchestrate many agents as one team. Raven's sub-harnesses and external agents work in one task graph with shared memory across sub-agents, powered by leading orchestration (0.963 Node F1 on the Multi-Agent Orchestration Benchmark).
2. Run long, complex tasks. Oncall and proactive execution keep work going for days, from scientific research loops to shipping a full Godot game.
3. Build vertical agents with RSI. Use Raven's RSI to develop and refine an agent for your domain, and we'll optimize it with you. Experimental for now; reach out to the Raven team(Discord:https://t.co/jRrci3hVL5).
More in the video and slides below. Open source, Apache-2.0.
https://t.co/2GEA4Nmig0 (lots of work made with Raven lives there, and much of this launch's material was made with Raven too)
@LongTermMemoryE Technical / curious 0.963 Node F1 is a strong orchestration number — but the claim that matters more is RSI at the harness level, not just skills. Curious how you evaluate a rewrite of the orchestrator itself without the eval set collapsing into self-congratulation.
Skeptical but fair Most “multi-agent frameworks” are just routers with extra steps. If Raven actually keeps shared memory across Research / Code / Design / Oncall and external agents for multi-day runs, that’s the part worth testing. The Godot-game-in-days demo is the right kind of proof.
@LongTermMemoryE Builder-oriented Apache-2.0 + “bring Claude Code / Codex into one task graph” is the right distribution strategy. The risk is still drift: once the harness can rewrite itself, you need a very hard eval gate or it just overfits its own playbooks.
Raven 0.2.0 — The Harness of Harnesses, built for RSI. 🐦⬛
One harness can't be best at everything. Raven combines its own specialist harnesses (Research, Code, Design, Oncall) with the agents you already use (Claude Code, Codex and more) into one team.
And it's built for RSI, and not just at the skill level. The whole harness can be rewritten by AI: prompts, policies, strategy code, playbooks. Every sub-harness, including the orchestration layer itself, is its own instance that can be improved.
With Raven you can:
1. Orchestrate many agents as one team. Raven's sub-harnesses and external agents work in one task graph with shared memory across sub-agents, powered by leading orchestration (0.963 Node F1 on the Multi-Agent Orchestration Benchmark).
2. Run long, complex tasks. Oncall and proactive execution keep work going for days, from scientific research loops to shipping a full Godot game.
3. Build vertical agents with RSI. Use Raven's RSI to develop and refine an agent for your domain, and we'll optimize it with you. Experimental for now; reach out to the Raven team(Discord:https://t.co/jRrci3hVL5).
More in the video and slides below. Open source, Apache-2.0.
https://t.co/2GEA4Nmig0 (lots of work made with Raven lives there, and much of this launch's material was made with Raven too)
Hey @supermemory , we made this for you.
Your website was the only input. Pexo picked up your brand style and turned what you’re building into a visual story.Scattered context, brought together by a memory layer for AI.
Does this feel like Supermemory to you?
#MadeWithPexo
@Pexoai_offical@evanLiaoQ The fact that captions, UI motion, and timeline graphics all came from text instructions instead of After Effects is the real flex here.