Do we still need dashboards, menus, buttons and complex applications? Or will the AI itself become the main interface, with a simple visual layer only for things like monitoring, approvals and seeing what’s happening? I’m curious how you see this evolving over the next 5 years. Will we still use software, or will we mostly talk to software? @David McDermott @Ari Evergreen @Jake Van Clief @David Vogel @Matthew Creamer @Bas Rosario

Been heads down on something the past month plus. Not a lesson, nor a Tea round but more like the layer under all of it. Kept seeing the same thing in comments and onboarding calls: People not knowing where to even start or if something’s already been covered somewhere in here. We're working on fixing that. Not ready to put it in your hands yet.

I've been part of this community and see all of the use cases and projects. I've tried to implement, but the truth is I don't understand it enough to use it successfully. I've been more frustrated than anything. To see what's possible from the community, but not be able to execute it is driving me crazy. What am I missing? Can someone help? How did you learn and master it? What was your process? I've tried on my own and I'm tired of failing.

You can put two people in the same AI chat session — Linux has had the tool for 20 years In short: => ICM on a linux server - all files and folders that are shared with others live here => co-workers connecting to this server and working with the files and folders => tmux allows shared chatrooms with AI agents Most AI coding tools give you a private conversation. You and the agent, in your own window. If a colleague wants to see what you are doing, you screenshot it or you paste it into chat. There is a much older way to solve this, and it turns out to work beautifully with AI agents: tmux. What tmux does tmux is a terminal multiplexer. Two useful things about it: - A session keeps running when you disconnect. Close your laptop, come back tomorrow, everything is still there. - More than one person can attach to the same session at the same time. That second point is the interesting one. Two people attached to one tmux session see the same screen, live. Not a shared screen recording — the actual terminal, for both of them. What that gives you with an AI agent Run your agent inside a tmux session instead of a plain terminal, and the conversation becomes something several people can join. Anna starts a session for the website redesign. She asks the agent to go through the stylesheets. Ben joins twenty minutes later, sees the whole conversation already there, reads what has been decided, and types the next question himself. Same agent, same context, no handover meeting. When Anna closes her laptop, nothing stops. The session lives on the server. Why this is worth knowing The usual way to get shared AI sessions is a hosted platform: your conversation lives on someone else's servers so that several people can reach it. With tmux you do not need that. The session runs on a machine you already have — a small Linux server, a virtual machine, whatever your team uses. Nothing leaves it. For anyone working with client data or under data-residency rules, that distinction matters more than any feature.

Yes. I’m being forced to the dark side. I’m looking to push all of our learnings we have here into the framework of what’s possible inside Enterprise security. My first step is to add this post to the community and see if you will drop wisdom, repos, and guidance in the comments. Thank you kindly.