I replaced Viktor in Slack today. And from my previous post - Claude shipped the coding to slack. I can now Code, Analyze my entire web app MCP and more! Viktor was our assistant running everything through paid API calls, and the bill climbed every time he answered a question. Now an agent sits in the same channel. It runs on my subsidized two hundred dollar per month plan, connected through OAuth instead of an API key. The API rate for this same amount of work runs about five times higher. The agent writes code and drops the exact error message in the channel the moment something breaks. It reaches my server through MCP to fix Amazon Ads campaigns without me opening a dashboard. My team logged into the same account and got the same access. No extra seats. No separate keys. No waiting on me to approve a fix. Pain is watching a bill climb for work a subscription already covers. Gain is full engineering support living inside the chat window your team already checks all day. Most companies are still paying five times more for less access than this. Should I go live and how you how it works?

Wow. Check this out! Slack Code — what it actually is and why it matters Slack shipped agent channels. Here's the whole thing in plain English. You mention an agent in any channel and it spins up a temporary code channel. That's the workspace — you, your team, and the agent in one room instead of you alone in a chat window copy-pasting context back and forth. And that's the real unlock: the agent opens with your team's context already loaded. The conversations, the decisions, the files. It isn't starting from zero every session like every other AI tool you've used. That's the difference between an assistant and a coworker. Four agents run inside it right now — Claude, Devin, GitHub Copilot, and Vercel. You don't need to be technical. Watch what the agent builds, look at the preview, type "make the button purple." That's the entire workflow. If you can give feedback in a Slack thread, you can drive this. Nothing ships without your sign-off. Same security stack as the rest of Slack — EKM, DLP, Discovery APIs. You review, you approve, then it goes. When the work is done, the channel archives itself. Context stays searchable, your main channels stay clean. Why I'm posting this here: this is the glue problem solving itself in public. The bottleneck was never the model — it was that every tool started from scratch and lived somewhere your team wasn't. Slack just moved the agent to where the context already lives. Full breakdown: https://slack.com/features/code-channels If your agent had your last six months of Slack loaded on day one, what's the first thing you'd hand it?

Hey All. Here is a glimpse at what you can expect to build for yourself, or your clients. We will discuss in more detail exactly how to get here. This is a business web app. Over the past 18 months I Have built out multiple webapps that serve my Agency and Client's Business. I learned the hard way how it should be done. But look at how beautiful this webapp look. You can give your team access to each section depending on what their job title is. You have complete control over the business knowledge (Using the folder structure on the back end) and the Data. I can't wait to share with you how to get this completed quickly!

Hey All! Thanks for joining. I'm dedicated to creating high quality content related to practical ways to enable AI In your business. I'm currently transferring my courses over from another platform. I hope to have it done in the next week. Thanks for your patience!

Let's get to know each other! Comment below sharing where you are in the world, a photo of your workspace, and your career goals. 😊