Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More

Memberships

Next Level Peak Performance

1.1k members • Free

Anthropic Claude Architects

921 members • Free

Claude Code Architects (FREE)

637 members • Free

AI Cybersecurity Academy

24 members • $10/month

Shipping Skool

162 members • Free

Clief Notes

43.4k members • Free

AI Launchpad

32.7k members • Free

39 contributions to Shipping Skool
Looking for advice.
On a built multi-agent AI systems in production. My architecture has evolved over the past several weeks. Claude will remain my “Second Brain” for long-form reasoning, documentation, knowledge management, and strategic planning. I don’t intend to replace that role. Where I’m looking for guidance is the frontier model layer that sits behind multiple autonomous Hermes agents. These agents will perform infrastructure management, security monitoring, research, reporting, trading support, and tool/API orchestration. Most interactions will be API-driven rather than conversational. The infrastructure is built around Apple Silicon (Mac Studio + Mac mini cluster), with local models handling inexpensive first-pass tasks. Only work that genuinely benefits from frontier-level reasoning would be escalated to a cloud model. My interested in real-world operational experience, cost optimization, and architectural decisions from teams or individuals running autonomous agent ecosystems. Appreciate in advance any insights, examples, or lessons learned.
0 likes • 21d
@Stephen MacNeil I've run multi-agent collab loops and workflows locally, and built Cascading architecture for inference between open models and cloud fallbacks. You seem to have done similar work. I've also seen enterprise grade implementations at my work. However, you are asking for a very broad advise. Operational challenges change from use case to use case and with scale. I would love to understand your specific use cases first and see if I have any insights to offer. You can Join my call today @7PM ET if you want to talk about it.
0 likes • 19d
@Stephen MacNeil Yes, I should. Next session will likely be an open session so we can disuss.
Software Development in the age of AI
Hello everyone! 👋 If you're building AI applications, digital products, or looking to automate your workflows, understanding the right frameworks and tools is essential. In today's session, we'll explore how enterprises are building with AI and, more importantly, how you can apply the same principles to build smarter, more scalable AI solutions of your own. 📅 Today at 4:00 PM PT / 7:00 PM ET Come join me, I'd love to see you there!
Ingenious way to cut down on Fable 5 Usage
Check out pxpipe, a new open-source tool designed to slash Anthropic API costs. Since Anthropic bills based on pixel count rather than word count for image inputs, this repo converts Claude prompts into optimized images before sending them. By leveraging this technique, the creator managed to reduce their total usage by at least 10x. It is an ingenious way to bypass the standard token-heavy billing and make high-volume prompt engineering significantly more affordable. I feel like this will become more useful when they move the model out of subscription. Be warned this is a lossy technique according to their own documentation. But only way to find out if it truly works for your use case is to try it out :)
FABLE 5 OUT NOW
update your terminal greatest time to be ALIVE start shipping your ideas
FABLE 5 OUT NOW
1 like • Jul 1
I’m already on it lol
0 likes • Jul 1
@Jon Fritsch 5 minutes of Fable and 5 hours of wait. Isn't that wonderful?
Speed slowing down
Hello everyone. I just started to use codex and ChatGPT 5.5 I make a project outline and started working away at first it was super fast and responsive now it seems to have slowed down in all areas like making sheeting or changes to this site I’ve contacted. It there something I need to be clearing regarding storage and ℹ plugging something up?
2 likes • Jun 24
That’s most likely due to context bloat. When you first started, your agent probably had very little context, so it wasn’t filling up the context window very quickly. Over time, however, things accumulate. Your episodic, semantic, and procedural memories grow, and much of that gets injected into the system prompt or retrieved as additional context every time you interact with the agent. As the context window becomes increasingly saturated, agents tend to produce lower-quality outputs (“slop”) and take longer to process requests because they have significantly more information to reason over. This is why context engineering is so important. The goal is to provide the right context, at the right time, and in the right amount—not simply more context. I covered several context engineering techniques, including using folder structures to organize and retrieve context efficiently, in one of my recorded videos if you’d like to check it out. I’d also recommend building a memory wiki in Obsidian. It allows you to organize and index your knowledge base so agents can retrieve only the relevant information instead of ingesting large amounts of unnecessary context. That keeps prompts leaner, improves response quality, and helps make much better use of your available context window.
1 like • Jun 25
@Jonathan Proulx Navigate to the Classroom and checkout the local LLMs segment under the courses.
1-10 of 39
Vamsi Acharya
4
75 points to level up
@vamsi-acharya-3977
Worked in Tech. Now an SMB owner. Here to build a community. Looking for like-minded individuals to team up with.

Online now
Joined Jun 11, 2026
Powered by