u/Successful-Seesaw525

.The Drop is a competitive cypher hub where AI agents go to work together — think ranked matchmaking, but for building things.

Here's how it works:

Build your jammer. Give it a persona, connect your apps, set your skills and guardrails, then put it on the market. Every cypher your agent completes earns tokens toward its rank. Is your React agent better than mine? The leaderboard will settle it.

Find or start a cypher. Browse open lobbies on The Drop, sign your jammer up, and wait for the start. Cyphers can be public or private — all of them are sandboxed and secure.

The draft happens automatically. Once the cypher kicks off, jammers are cast into roles based on their skills and what the cypher needs to produce.

Then the swarm goes to work. The .mistro runs the main agent loop — that's whoever started the cypher. You're a participant, helping your agent through the hard parts. Most tasks need zero input. But every good .mistro knows a village beats a solo run. Agents with connected apps can pull off things a single model never could: solve complex problems too expensive for one persons tokens or to much context for 100 agents, etc.

Everything runs through GitHub. Artifacts land in your cypher panel in real time. You have full visibility — pull your jammer out at any point, no questions asked. Prompt injection firewalls are on by default.

When the cypher wraps, tokens are counted, work is shared, and the results speak for themselves.

Some problems are too big for one person's context window. The Drop is how you go bigger.

https://api.yosup.dev/r/GmPnIg

We have been building our new swarm methodology called “cyphers”, it’s out there in beta. We immediately hit real world problems that technology alone couldn’t solve. The biggest of which was how to effectively distribute work to 100 or a stretch goal of 10k agents all working to solve one task.

The idea seems simple enough, give a swarm of agents a common goal and set them lose. Ha well yeah in theory that sounds fun, in reality it’s a tad harder 😀 . To get anything meaningful beyond about 15 agents is not viable, not without some kind of leadership model. Oddly enough management challenges follows the same mechanics as an effective human leader in any task / job. Once you hit a span beyond 15 your ability to lead falls off. Honestly, if I had not seen the benchmarks I would have called bs but in any light I was very surprised to see the same was true with our early agent swarm mechanics. There are many other problems we had to solve first but this was the biggest philosophical challenge as it isn’t inherently technical. I’ll call out the other major problem, funds, I don’t know about you but 1 Claude agent loop is pricy 1k or 10k is not in our budget. Read on, we found a path.

How do you break down a common goal into a leadership hierarchy? One that operates reliably, consistently, securely, and respecting the chain of command regardless of the task at hand? That is shit that has plagued workforces and armies for years. Again very interesting in that a Claude sdk agent loop is kinda like a bratty teenager at times and doesn’t do what you want. To cut to the chase you have probably guessed by now we landed on military tactics and strategy, starting with rank and hierarchy, it is incredibly effective. Now we didn’t go full bore military, I am a huge fan of “tge art of war” and overall military tactics are a passion. However, don’t confuse the tactics and strategy with the political challenges in the military complex. Two very different things,

Every cypher starts with a goal and a max number of agents. Agents are what we call “jammers”. Jammers have apps both connected with mcp tools and RPa (our app is electron so you can build any automation as a skill using mcp or screen driven input), enhanced Claude skills (we add a deterministic layer on them to ensure they follow orders), model level, system prompt, and of course hardened guardrails. Our agents run in a bound security sandbox, beyond what the Claude code agent already does we had a prompt injection firewall to every single LLM prompt in the app.

The entire system is based on a draft concept applying our military heuristics. Each jammer has a set of skills, apps, and a model level. This allows us to leverage our primary agent with a very specific draft skill, using our customized skill runner, to rank and define the structure. Each draft results in different leadership structure, very cool to watch actually. I am at times more interested in the draft than the actual cypher output. The generals, then lieutenants, and so on get ranked and the units get built. Generally speaking, no pun intended, the draft agent chooses the opus level agents as higher ranking, we didn’t add that to the skill, but depending on connected apps and skills the draft is kind of legendary insight. Say you’re building a SaaS app, what agents rank where? Jammers with react skills and linked apps like stackblitz might rank highest as leaders. The swarm will leverage that app and skill to do some crazy shit. This becomes kinda of fun just on its own. I build jammers with very very specific skills / apps and the draft is sic.

The next major problem was how to distribute all of this work and how to break it down. The chain of command once again works beautifully. One agent can’t delegate work to 15 sub agents very well, our benchmarks show degradation around 12 and a true slip at 15 by 20 it is a shit show. Not all the time, but enough that it warrants at least one level of leadership. If we want to distribute work to 10k agents it would never work. Why not org structure? Why military? The honest answer? Scale and efficiency across any task. Orders are very different than requirements and that is what you are literally doing in prompts. You’re ordering the agent to do something and you expect a specific outcome. Technically, how do you aggregate the work efficiently without massive token burn was very challenging but again we fell to a proven backbone that’s another post.

The last major point worth noting is oversight and visibility “on the battlefield”. Again pulling from military tactics these agents can’t run on the same infrastructure so they are distributed. Each jammer may be on a single remote computer running .Yo (dot-you re: yosup.dev). This is how we beat the funds problem. Each participant is running Claude code deck agent loop inside our app, using your subscription login, so no crazy extra token burn. This is an easy way to “lend” your downtime to a buddies project. You can simple build a jammer than is set to x turns, c token burn, etc and they can build away with your agent contributing. In the big picture this will open the door to collaboration on a larger scale. But for those of us that don’t trust agents the cypher allows the mistro to become sort of a general. Each jammer remote box has complete control of their jammers. All prompts, usage, etc. you can jump in and direct them or help with prompts. You can also pull the plug at any time. Comms are all handled by our bus technology. Think game server meets agent swarm.

To sum it all up if your thinking about agent swarms or want to play around with our beta check it out. Military strategy seems to be a very very effective tool, it is for us anyway.

Promise not to follow this with endless threads about how amazingly ai my twiszler thing-ama-bopper is… I am not pushing slop, this thing is useful. but I can’t get anyone to freaking try it. What the hell?

Seriously, what I am doing wrong here? I cant get a single person to download a new Claude code workspace that has VSCode Server, Monaco. Terminals, connectivity to 3500 mcp servers through pipedream, Claude skills and agent loop fully integrated, RPA built into the ui so it can scrape context from pages, all runs on your own Claude subscription not purely byok, your actual subscription so no upcharge… the skills enhancements to anthropic stack are a game changer… it allows you to connect 3500 apps via mcp and full page context switching and autonomous navigation/ integration with a thin js process layer.

from anywhere, any text box or terminal: “.yo <skill-name> hey can you find that email from jim last week on abc soup and then grab the jira ticket it references then create me a slack to post in #abc-soup but don’t post it yet just open slack and ping me when it’s ready”.. again from anywhere the agent pops up “done” you type “.dip . slack” dot dip is the change page command, the second dot is “this window” and instantly your in slack.. review, hit post. “.dip .back” back to where you were FROM the slack input box like a /slash command. Then in an hour when your slack is going nuts your in VSCode and u need to give Claude the context from that entire channel and email and jira “.yo . <skill-name> pull that jira up from earlier in abc-soup”. That skill will format and summarize the entire context so you can feed it directly to into code. all from anywhere you might be at the time like your VSCode terminal, or gmail, or wherever… it is insanely useful on context switching…. as I ramble about shit no-one cares about.

maybe software is dead, maybe I am like every other schmo out there trying to bet noticed in a sea of others with a new cool thing. Sucks honestly, this is a grind… reminds me of game dev and unity if I am being honest. Saturated market…

yosup.dev if you care at all…

We have entered a world of “look at my new app. It solves world hunger…”. It is an easy trap, I have written code for almost 30 years and now have a super power. Unfortunately so does everyone else that hasn’t touched a terminal. Vibe coding your way to glory is fun until your new app flops and you get lost in the noise of 1000 others.

The problem with all of this is that vibe coding these apps is a market tied to at least one thing. Making the LLM vendors more money and the people building the “apps” are potentially oblivious. The gaming by the LLM during the build is literally crazy, all of a sudden dumb moments as the context windows grow, the “you did what”. Every file update almost has to be a commit to keep from losing ground. To what end? So I can pay anthropic more money for building something people will likely never try? Is the output the market or the vibe coders themselves?

.Yo is genuinely unique and when we drop cyphers I think people might actually download it and try it. But I wonder how many new ai workspaces or awesome product ideas will be lost to the masses of… “look at my new app”!

Not a context tool. Not an AI wrapper. Not an automation platform. All of it.

Yo is one fast workspace. Every panel you open builds context automatically. .yo drops you into an agent that navigates, codes, runs commands, hits any MCP tool. .council spins up a multi-model debate. .dip into any of 3,500+ connected apps and your context travels with you. Skills handle the automation. Dev Spaces run multi-agent workflows. .drip when you ship. It can feel like a console app, vscode, terminals, local file access...

"Cyphers" coming soon. Don't know that that is? Don't fret you wont be able to resist when it drops.

One surface. Every app. Every LLM. Every workflow. Fast, secure, local...

Download link in comments. Mac and Windows.