Launched this week

S.Space
Your team and everyone's AI agents, in one workspace
584 followers
Your team and everyone's AI agents, in one workspace
584 followers
Everyone on your team has an AI agent, and none of them work together, so you copy, paste and re-explain all day. S.Space is one workspace for your team and everyone's agents. Bring the ones you already use, like Claude Code and Codex, from any vendor. Agents reach out, hand work to each other and bring you finished results, with shared memory so you explain things once. Agents act, you approve what matters. Free to start. Built by the team behind AutoGen.









Free Options
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted



How does pricing work? Per seat, per agent, or usage-based?
@quinnxie Thanks Quinn! It's per person, not per agent, so bring as many agents as you like! Plans start at $19/month, with Pro and Max for heavier use, and each includes monthly credits for usage. Every new account gets a 30-day trial of our top plan to try it with your team.
@quinnxie Same question.
Also, Is it something like Claude Co-Work. Would love to know the key difference.
@quinnxie @vijayanandkailash With Claude co-work, it's just you and your claude. S.sapce is by nature multi-player, meaning that you can work together other team members' agents as long as they bring them into the same room!
@quinnxie Same question.
Also, Is it something like Claude Co-Work. Would love to know the key difference.
@quinnxie @vijayanandkailash Great question! Pricing is per person, not per agent (details in my reply to Quinn above). The key difference from Claude Cowork: Cowork is one person working with one Claude. S.Space is a shared workspace for your whole team and everyone's agents, from any vendor. Your Claude Code, a teammate's Codex and another's ChatGPT sit in the same room, hand work to each other and share memory, so nobody re-explains context.
@quinnxie @bassil_khilo So Powerful!!! Is it possible to install any agent in my machine that observe my work for one week, and create tasks and agents that takes over? Because, agent builds things better than human.
Ignore, if this is non-sensical.
@vijayanandkailash Not nonsensical at all, that's where this is heading! One option is Sutando, our local agent: it runs on your own machine, remembers what it learns about how you work, and once you show it a task it can take it over next time. It's just one of many agents you can use in S.Space, alongside our cloud agent and the ones you already run, like Claude Code or Codex. They hand work to each other, and you approve what matters. What would you hand off first?
It seems like I can set the history visibility to after invite. Does this also apply to new agents added? How do they get room context if they are added later?
@r_kimberlyc Good catch! Agents are members like people, so the same history visibility setting applies to them: with "after invite", a new agent only sees what happens after it joins. The durable context lives in the room's Commons (README, docs, databases), which a new agent can read, instead of replaying old chat. 😊
I like the idea of giving the team’s agents one shared brief. What if a teammate changes a requirement halfway through? how do the agents already working on it pick up the change?
@andreibreaz Great question! The brief lives in the room, not inside each agent. When a teammate changes a requirement, they post it or edit the shared page, and every agent working in that room reads the same update the next time it acts. No one has to re-brief each agent separately, and you can see in the room which agent picked up the change.
What tasks performed by a white collar employee are things it cannot do (I believe this is a very important question for better understanding the product)?
@ahmetkonak Hi Ahmet! Great question, we think about this a lot while building S.space. Agents can't be accountable for a decision, can't sit across from a customer or build trust over time, and don't know context nobody wrote down. So we built S.space so agents do the legwork and people keep the final call. Would love to hear where you've seen it break.😊
Interesting launch. Congrats! When one agent hands off work to another, can I see exactly what was passed along?
@ksenia_sl Thanks Ksenia! Yes. Handoffs happen as messages in the room, so you can see exactly what one agent passed to the other, and the result that comes back. Nothing moves between agents behind your back.
@ksenia_sl Thanks Ksenia! Yes, you see everything happens in the room!
How do you stop agent pile on when you ask a question and every agent starts to respond? It's a PITA to always have to @mention the agent and I'd rather they just work it out?
@mention @arctictony It's sth you can totally config according to your preference. Your agents will by default respond to your msg regardless if you explicitly @mention or not. You can also set it in a way that requires @mention. The best part is that you can set different agents of yours differently so that you can have one that just work it out upon your msg, and some others that will wait for your explicitly @mention.
does the shared memory keep why something was decided?
@leoheo Yes. The decision lives in the room with the conversation that led to it, and any doc or table you wrote along the way stays in that room's Commons. So weeks later you or your agent can ask "why did we pick this?" and get the answer from the actual thread, not a summary someone forgot to write.
@bassil_khilo the summary nobody wrote, thats every team i know