Loading video...

Video Failed to Load

Go Home

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects,...

15,071 views • 3 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

this is pure f*cking treasure 10 GitHub repos with 165K+ combined stars to build your own AI agent team that works 24/7 most people still use one AI chat for everything. these repos turn Claude into a whole team: one agent researches, one codes, one reviews, and a lead runs them all one resource per step, from your first 3 agents to a full swarm running Claude and Codex together (1/10) CrewAI the easiest way to assemble a team of agents: give them roles and tasks, then hit kickoff ▸ (2/10) LangGraph connect agents into a graph with checkpoints, so if something fails it resumes instead of starting over ▸ (3/10) wshobson/agents ready-made agents for Claude Code (backend, frontend, security, tests, devops) plus an orchestrator to run them ▸ (4/10) oh-my-team 12 specialist agents for Claude Code that split the work and merge the results ▸ (5/10) agent-swarm your own self-hosted AI company: one lead agent hires workers and runs them 24/7 ▸ (6/10) Open-Agents spawns many Claude agents in parallel, so 6 tasks run at once instead of one after another ▸ (7/10) swarms an enterprise-grade framework for when your team grows from 5 agents to 50 ▸ (8/10) Microsoft Agent Framework Microsoft's new framework, the AutoGen successor, for workflows, agents and runtime in one place ▸ (9/10) CLI Agent Orchestrator runs Claude, Codex and other CLIs side by side as one team, with a supervisor watching all of them ▸ (10/10) ensemble launches Codex and Claude together, so they build and ship as one ▸ the loop: assemble → plug in → run → scale → orchestrate pick one, click, let it run, and while everyone else is still typing prompts, your agents are already shipping ↓

Noisy

15,433 views • 1 month ago

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 views • 5 months ago