u/Successful-Seesaw525

I am one of the founders of glyphh.ai…

Explainer video as promised, AI generated by using glyphh. 100% dogfood, built a glyphh skill and tasks with multiple agents in the loop. Gemini for images, runway for video and avatar, plus my face … eleven labs for audio! All from one app, one workspace.

Every work panel in glyphh is a semantic app wired into any loop you want to run. So build your own apps, your own tasks, agents, sills, graphs and Ada models. It will change how you vibe.

Use your subscription with glyphh by running any cli you want : Claude, Codex, Gemini, Cursor, Co-Pilot, and glyphh (requires a subscription for our model router).

Would love feedback and features. Find us on discord also.

Full disclosure I am the founder and one of the lead developers of Glypph.ai. This is a pitch esk post of something I built using Claude and my 30 years of software development experience. So if you bail here, totally cool.

What is your super power? Serious question. What super power do you wish you had? What if you could combine every super power you can think of into one thing and yield it at the right time to achieve any goal?

Glyphh combines your apps, models, and workflows into workspaces with predefined agent rosters you can utilize deterministically to get shit done! How? By creating a new type of app surface, above skills and below micro SaaS. Semantic Apps are not AI slop but the inverse, they are specifically designed to reduce ai from the app tier. Only use and alLM when you have no other choice, and if you do need it, be precise on the expectations and guardrails.

Our goal is to use less AI in every way during the runtime or said another way to extensively use AI during the build phase using a mini SaaS delivery framework where YOU build apps that can instantly extend the glyphh harness with rich ux, connections to literally 3500+ apps, and model / slot filled loops. The result isn’t a headless world filled with massive .md files trying to get quality out of probability BUT usable software built reliably through successive approximation in an a well scoped build / release process.

Bounce from one workspace to another as your models, slotted loops, agents, and rich ux follow you. Always pre loaded with a fact tree of semantic data that encompasses what you’re doing durably across turns. Turns that can “rover” LLMs on every forward pass…

Build anything you can think of, host it on glyphh in seconds, collaborate, corporate/ org level approval gated marketplace built-in governance.

Full disclosure: I'm the founder of Glyphh AI, and yeah, this is a pitch. Stop reading if that's not your thing. We used claude extensively in building the solution, now we build with Glyphh using claude inside our own app as a slotted model.

The video is the Glyphh Desktop aka our Harness!

A few years, a lot of iterations, and a real thank you to the beta testers who lived through the early builds. Glyphh v1.4.2-beta is finally live on the new UI/UX.

Serious question: what's your superpower? What one do you wish you had? What if you could combine the powers of every super human ever, into one? One that you could control...

We combine the powers of every model and tool you've got and direct them at the right time, in the right order to become incredibly efficient at a specific task.

Under the hood we turn your apps, agents, and workflows into slot-oriented loops we call rrotors (recursive reasoning on top of reasoning systems). They run on a patent-pending HDC architecture, the glyphh HDC lattice. Rrotor is the agent runtime that hands semantic app capabilities to the harness.

You can build native Glyphh apps that mount straight into the desktop app — the MCP tools you build are wired to the agent loop instantly. With 50+ models across a dozen-plus providers, you build rrotors custom-fit to how you work. The harness adapts to you: build the tools you want, the UI/UX you want, slot the models you want.

That's the whole idea not another chat harness, a runtime you shape into your own superpower. And it keeps working every day, 24/7, even when you're not at your box.

I'll add the link in the comments if your interested in checking it out.

Full disclosure: I'm the developer behind Glyphh, and this post is to show off what I built — using Claude Code and 25+ years of software engineering experience.

Every context switch costs you about 15 minutes in lost productivity. I wanted an easy way to bring my agent and its context with me without losing the thread — so I spent the last two years building Glyphh. Thanks to everyone who provided feedback and testing on the open-source version available on GitHub!

The idea is simple: combine a rich desktop UI/UX, loop selection, model slots, and app building/publishing in one vendor-agnostic solution. The result is incredibly productive workflows tailored to you — the way you work, your usage, your needs. Not a one size fits all solution.

You can bring your own keys, including open-weight models. I used Pipedream Connect to open connections to 3,500+ MCP servers, all agnostic to any provider. And you can switch your layout anytime without changing IDEs or how you work.

Build an app, scrape a page, automate a task, pull your agent up in any app anywhere your working and your context across all your sessions is right there with you.

Check it out: glyphh.ai/products/desktop

What is Glyphh?

Glyphh is an IDE, a vibe-coding workspace, an AI OS connected to every app you work in natively, and a vector-DB capture store — with workflows, RPA, automation, and 3,500+ connections through Pipedream, all in one desktop application. Swarm across any provider you want. Or point Claude and Cursor straight at Glyphh and build from your own IDE, with everything Glyphh knows coming along for the ride.

How it works

Download and install Glyphh on your machine. It's free forever — no markups, no token games, bring your own keys. The only thing we charge for is the 3,500+ MCP connections via Pipedream, because that part costs us money to run. That's it. No AI slop.

Open any app you already work in, switch contexts without thinking, and stop losing your flow.

The one big sell i have!

There is a command language that once you pick up allows you to switch apps and do things you didn't know was possible in ways you will really appreciate. Things like instantly open an app by just typing .dip <app-name> or .dip <app-name> .waz <function> anywhere in any text box.

These may seem silly but in any text box in any app your working in you have access to claude or any agent you build, any skill, any workflow, +3500 connect mcp apps, RPA, and endless ways to connect your personal way of working!

All of your context is right there: .yo > hey can you find that email from so and so and then find the customer, pull up jira and pull that prd into claude and prompt it to build out a plan. In the meantime you can .dip to your slack layout or coding workspace while that is happening. The assistant and your codex are wired in the same agent loop on the same context!

Why we built it

We're 25+ year software people, and we were tired of context switching. AI was supposed to help — instead it multiplied the tab-juggling 10x. We wanted an assistant that didn't force us into one way of working: one that comes with us into every app, in its native experience, instead of dragging us into yet another chat box.

So we built it.

Where to get it

glyphh.ai — free to download and use, forever.

I am cresting 25+ years in software. If I count when I wrote my first Apple script at 7 that number is much larger 🤣. Professionally, I have traveled the globe, became a P.E. at Oracle / Sun Microsystems ( they called principal field technologist back then re: pe for services) at the age of 28 (don’t quote me on the age), patented sso tech from an American Airlines project 2 years before that, been acquired more times than I care to admit, still working so there is that 😱

The reality is my brain moves fast, too fast, so fast in fact that I tend to lose people very very quickly. I often find myself chewing up too much air, and trying to use too many words to break down where I lost folks, which in turn chews more air. A curse and a gift in the same wrapper… It is the one gift I think I was truly given outright, the ability to see the big picture, or a big picture anyway, and work back into a plan of attack almost instantly. My success was based on a fail fast strategy before I ever knew what was and I did fail often… software development through successive approximation. The key insight was that no-one but me ever noticed!

To that end my ADDHD brain loves this kind of crazy AI dev mode. Game recognizes game, finally insanity to match my pace, the results, ahh well I vibe freaking everywhere… my wife hates it! Hehe it is addictive, highly.

My point is that in a world where everything is generated good ideas are still good, bad ideas are still bad, but working on them at this pace is, well, freaking fun!

Anyone else feel this way?

.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.