User
Write something
Setting up AI Agents for Businesses
Hi everyone, so glad to be here and have loved watching Nick's videos. I really want to pursue setting up and managing Hermes agents for small businesses just like Nick explains but just have a few questions: 1. How exactly do we go about setting up a Codex plan for them if I want to cover the cost. Do I have the Codex plan under their email but my card? Do I just create a new Codex account with a new email and then pay for it that way? 2. Do we set up Hermes agent with Honcho for short term memory and then also a Obsidian vault for long term? 3. And on a technicality, when managing a client's workspace in Orgo, when the client is using the agent on their end through channels like Slack, Telegram, etc. can we technically see and have access to the information they are working on? This part has kind of confused because don't know if there are any privacy or confidential issues at play here. Thank you so much and answers to any of these questions would be much appreciated. (P.S. It would also be great if anyone knew of a good resource I could use to set up my own Hermes Agent that would basically be able to monitor and fix my client's issues when they arrive)
2
0
Sell AI Employees to Small Businesses (just steal mine)
I just built a full AI employee from scratch in this video. Everyone’s hyped on agents but barely anyone’s actually showing how to build ones that can really work inside a business. Here’s the entire stack I spun up live (no holding anything back): • Cloud computer running Hermes on Orgo • Its own email (AgentMail) • Its own phone number (AgentPhone + iMessage) • Telegram as the main chat interface • Every tool & connector hooked up through Composio • Credit card so it can actually spend money • Obsidian vault as its knowledge base / second brain • Latitude for observability so I know when shit breaks I made one main orchestrator agent (named it Hubert) that stays in charge 99% of the time and just hands tasks off to specialized sub-agents underneath it. One giant bloated agent is a nightmare to debug. This way everything stays clean and purpose-built. Full live build, every prompt I pasted, every terminal I opened… it’s all in there. And I’m giving away the complete templates for the orchestrator + every sub-agent I build going forward. I'm giving you actual employees that can do real work. Watch the whole thing here: PS - the template is free here on Github: https://github.com/nickvasilescu/nicks-stack
Hermes Agent on Orgo - Practical Guide
Hey guys, I've decided to launch a mini course on deploying a Hermes Agent on Orgo and configuring it for a client, including a step-by-step checklist with copy/paste commands. Wanted to offer it for free to you guys for feedback/testimonials. Please let me know if you're interested!
I cloned Grok Bot in an afternoon.
Here's the full stack (and the business hiding inside it) Last week Grok Bot cut everyone's usage limits. I run 8 bots on it. A chief of staff, a Skool moderator, a Slack drafter, a YouTube comment bot, a Bookface outreach bot, and a few more. Overnight, all of them were rationed. So instead of waiting for xAI to fix it, I tried something different: I had my agents reverse engineer Grok Bot and build me my own. It worked. I recorded the whole thing, every prompt, start to finish. Video is below. Here's the breakdown. What actually happened 1. The design. I pointed Claude Opus 5.5 at the real Grok Bot app on my Mac and told it to click through every screen with computer use, then rebuild it in Paper MCP. About 30 minutes later I had a near pixel-perfect replica: same screens, same icons, same layout. 2. The backend. In parallel, a second agent ran the Reverse Engineer Anything repo (443K stars on GitHub) on a Linux cloud computer and mapped how Grok Bot works: the bots, the API, the interface. 3. The build. The build agent read the design thread, read the architecture, and built it. A couple of hours from my first prompt, I had a working clone. Google sign-in, Grok 4.7 behind every bot, app connectors, routines, and each bot on its own cloud computer that I can take over and control. While all that ran, a third agent on a GPU box edited the video you're about to watch. My MacBook never got warm. The stack - T3 Code: where the agents live. One workspace running Claude and Codex across 5 machines: my MacBook plus Linux, GPU, Mac mini and Windows cloud computers. - Reverse Engineer Anything: maps how an existing app works. - Paper MCP: design tool for agents. This is what nailed the UI. - xAI API: the models, voice, image and video, files, X search. Most of what Grok Bot is. - Composio: sign-in and every app connector (Gmail, Slack, all of it). - Orgo: a computer for every bot. (Yes, that's my company. It's also the piece xAI doesn't give you.)
New here, question on Claude subscription
Hey guys! It’s been a while since I’ve been watching your videos, and I’m really happy to finally be part of the community. I’m planning to try your Grok bot clone, but I wanted to check first that I won’t risk getting banned on my monthly subscription by using it. I was using Hermes back in January and got banned from Claude. Just curious what you think about it, and whether they’ve stopped banning people for using tools outside the official harness.
3
0
1-30 of 155
Agent Empire
skool.com/agentempire
Build, run, and sell managed AI agents for your business or for clients. A free community founded by Nick Vasilescu.
Leaderboard (30-day)
Powered by