Asked a colleague who runs the local 2600 club (https://malmo.2600.se/) if they had any vacant spot for a talker. Turns out they had one in about 2 months time, which sparked me into action and yeah got a crazy to build a proper "purple-team homelab". Purple = red + blue , where red = attacking team and blue, defending. meaning i have hackers (run by ai) attacking an enterprise AD structure that i've set up with services, servers and users, and i have defenders watching their every packet and footstep , detecting what the hacker did, when, where, how , and recommendation on how to prevent it. I Further developed GOAD, Game Of Active Directory into SAGA , Star wars Active directory Galactic Arena, to have more features and ways to deploy it. Basically i was trying to replicate Hack The Box - Professional Labs, but with ai. the tagline while building was "by ai , for ai" and it's been pretty educational , since i started it due to "AI FOMO" then it became this "frankenstein" of a lab where i've basically thrown in whatever that sounds like fun, from a cybersecurity perspective. and well, on friday i finally did it :) more people than expected turned up, and i think they liked it xD the presentation slides for those interested: https://malmo.2600.se/pages/June2026 (and for the extra nerdy ones, the architecture and more info lives at: https://kryssar.se/) my way to kind of "give back to the community" :)

This is a little bit of a rant cause I can’t post these thoughts anywhere else. At least, I’m not ready to get publicly crucified yet, so… I cannot talk to almost anyone I know about ai. They have no idea what’s going on, or about the kind of stuff we do. It’s all doom and gloom. There is something that really bugs me about it, beyond the naivety and half-glass-full mentality. It’s that... gatekeeping does nothing for humanity and is a selfish mentality at its core. So ai has access to lots of data, and artists data. So what? If you’re really good, it doesn’t matter. Great products, great services, great talent all have one thing in common which makes them in-demand. They’re great. And greatness is witnessed by all the people who consume their work. There’s no gatekeeping because it’s literally on display. From Harry Potter to Michael Jordon, Disney to Taylor Swift, Steve Jobs to Crayola Crayons. If no one is trying to copy you, then your work isn’t loud enough. Either because it’s not good enough (yet), or because you’re hiding it away from the world out of fear. In any case, their success came from being great, NOT from gatekeeping information or their talents and trying to sell them to the highest bidder. Bringing it full circle… Nobody lost money cause I finally had a tool that could do work for me for free. Rather, everyone in my companies will literally make more money because of massively efficient operations. It also means we’ll be able to afford remarkable talent with the extra profits we bring in due to that efficiency. I’m SO glad I have more options to take care of the people I bring into my sphere. One last thought… a little side quest here.. Whenever I ask people about why it isn’t a good thing that robots will be able to farm all the organic food we need at extremely low costs to produce compared to what we have now, no one has a good answer. I used to be of the mindset that really rich people should use their money to fix problems like world hunger. Then I actually looked at the challenge of getting the recipients to use money the way it’s intended, and started crunching numbers to see how long they could solve it for. Full stop, it doesn’t work. Because complex problems require complex solutions. A billion dollars solves world hunger for how long… a day? A week? A month? And then what?

Most of what I see in here is about automating tasks. Building workflows, connecting tools, making things run faster. I've been learning all of it and it's clicking.But I kept hitting a wall that I couldn't name for a while. I was using an LLM app as my operating system. Not just for tasks but for decision-making, project navigation, thinking through problems, tracking where things stood across different work. And it kept falling apart. Sessions ended, context disappeared, drift compounded quietly. By the time something felt wrong, I was already deep in the wrong direction. I lost real work to it. The problem wasn't the tool. The problem was the category error. A workflow system automates a process you already understand. You know the steps, you know the inputs and outputs, you want to run it reliably and faster. It's execution. It shines when the process is stable. A reasoning system is what you need before that. It's the thinking partner that helps you figure out what the process should even be, especially when you're building something from scratch and the process doesn't exist yet. You can't automate your way to a decision you haven't made yet. I was treating a reasoning tool like a workflow system. No persistent state, no routing logic, no structure, just conversation. It can't hold a project together. That's not what it's for. So I've been building what I'm calling CoworkOS, based on ICM principles, a folder architecture that gives Claude a stable structure to operate within across sessions. Routing tables, layered context files, memory that persists. The idea is: before you build workflows inside your projects, you might need an operating layer that actually runs the reasoning coherently. I don't know if this is the right approach yet. Still figuring it out. But the distinction feels important, especially if you're newer to this and trying to figure out where to start. Workflows are powerful once you know what you're automating. The reasoning layer is what gets you there.

You built your first folder. Vote below, then drop a screenshot in the comments so we can see what you came up with.

I’m running into a massive bottleneck with corporate clients right now. Because they’re handling market-sensitive data, their IT compliance teams have them completely locked down into Microsoft. No external APIs, no Claude—nothing. Ideal world would be building solutions in CC. I’m convinced the only real solution here is building custom tools and agents natively inside their system (Azure OpenAI, Power Platform, Copilot Studio, etc.) rather than trying to pitch external pipelines they'll just reject anyway. Has anyone actually built robust, advanced agent workflows strictly inside an MS-only corporate environment? Curious to know how you handled the architectural constraints, and if it's worth the headache of building inside their sandbox. Let me know what you've found works.