Campus - One project space for humans and AI agents
by•
Campus gives builders a shared space to build with teammates and AI agents. Keep your repo, terminal, project knowledge, conversations, and agent work together in one persistent workspace, instead of scattering context across Slack threads, docs, tickets, canvases, and one-off AI chats. Campus is organized around the thing you are building, so humans and agents can pick up where the work left off.
Replies
Interesting product
FlutterFlow
@madalina_barbu thanks Madalina, give it a try and let us know what you think!
I agree that most of the pain in juggling AI agents is rebuilding the mental map every time you switch tools. How Campus handles version history once a room gets busy, if an agent makes a change overnight, is it easy to see what happened and why?
FlutterFlow
@mshen316 great question! We always defer to git for version control, since we think it's the best technology for the job. So your agents can run overnight and provide you a visual of what they did, but you'll always be able to view git as the source of truth for its changes. At least that's what we'd recommend!
The "context is already there when you come back" bit is the real unlock — losing state between sessions is the tax nobody budgets for, especially with agents. Curious: when an AI agent picks up work in Campus, how much of the human's messy context (half-finished threads, abandoned branches) does it actually use vs get confused by? The dream is shared memory; the risk is the agent inheriting the mess too.
I can see this working really well as an individual, but it feels a little big brothery to do this as a team.
FlutterFlow
@john_joo haha that's a fair concern! you're able to select which of your screens to share and which to hide though, so I view this more as a tool to connect with your teammates when you WANT to share :)
The "scattered across Slack, docs, and one-off AI chats" line hit a little too close to home lol. As a solo builder I lose half my morning just reconstructing where I left off with an agent. Does the persistent workspace let an agent actually resume a task days later with the earlier terminal and repo state intact, or does it re-read context fresh each session?
@Alex Greaves that makes sense for the code side. Curious about the CRDT part though - when two agents both propose changes to the same canvas node at nearly the same time, does one just silently win, or does a human get a merge prompt like you'd get in Figma multiplayer?
@abel_mengistu Voted for Campus today. "One space for humans and AI agents" is a message that's easy to make abstract, curious how you're keeping the first email concrete.
FlutterFlow
@alex_iliescu thanks for the love!
I'm not sure I would be your target audience as my 9-5 is in construction project managment outside of tech, but honestly, I could really use this to keep track of multiple on-going projects without losing my space flipping between everything. Will show some colleagues and report back!
FlutterFlow
@elliot_zoellner ooh this is AWESOME! can't wait to hear the report :)
This is a really interesting direction.The biggest pain for me is usually not the actual building, but keeping the context together once conversations, tickets, docs, and AI chats start spreading everywhere.
How does Campus handle older project knowledge over time? For example, can a teammate or agent come back weeks later and still understand why certain decisions were made, not just what the current files look like?
Pieces for Developers
I like the idea, when you're running so many apps, you tend to lose context rapidly, and I think this is a good approach to solve that.
Trying it out today, awesome job folks!
FlutterFlow
@ialimustufa thank you! can't wait to hear what you think :)