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
Earth.fm
This seems like a big step towards making AI teammates more than just another chat window, and I'm looking forward to seeing how developers use it in real projects.
FlutterFlow
@1mirul 💯
We're also super excited to see what people use this for. Campus is engineered to be a sandbox for work, the rest is up to the user :)
FlutterFlow
@1mirul we are too - give it a try and let us know!
FlutterFlow
hey Product Hunt! Lydia here, growth lead at FlutterFlow.
i had three AI sessions running, a design file somewhere, a doc i couldn't find, and a teammate asking "can you share your screen?" for the fourth time that week.
on Campus, I dragged everything into one workarea: terminals, agents, the design file, the doc, and just kept working.
the REAL highlight for me are the memes. someone dropped a GIF mid-build and suddenly our remote team felt like we were actually in the same room.
Campus is in alpha and we want your honest feedback. tell us what's confusing, what's missing, and what would make you actually use this every day.
— lydia, FlutterFlow team
@lydia_lee3 on "in the same room" note: I really like those instant messages which you can trigger with "/". others seeing in realtime what exactly are you typing (with all the typos and backspaces) - really feels like we're in the same space not just virtually
FlutterFlow
@lesnitsky yesss it's so cool how we can stay connected across time zones!
Getting on campus to drop the most unhinged gif in the middle of a teammate's work area is now officially part of my morning 'preparing for work' routine 😅
Jokes aside - we're a distributed team, and this is the first thing that's actually made it feel like we share a space. Not a 'team bonding' tool, just a place where everyone gets their work done, and the connection happens on its own. And it's not just the humans: our agents are on campus too, which turned out to be weirdly great 🤖🤝🧑🏻💻
FlutterFlow
@lesnitsky unhinged gifs are a regular occurrence fr
FlutterFlow
@lesnitsky @lydia_lee3 & when music comes on that i didn't choose - that gave me a good scare the first time tbh
FlutterFlow
@lesnitsky @kate_usher2 validdd
FlutterFlow
@lesnitsky As much as I love all the other features and benefits of Campus, the team shenanigans are my favorite part :)
FlutterFlow
@lesnitsky @agreaves never a bad time for team shenanigans :)
One thing I'd love to see is a built-in versioning or git-style history view right inside the editor so I can visually compare UI states and roll back when a redesign doesn't land. Right now I'd have to rely on Firebase backups, which feels a bit clunky for quick iterations.
FlutterFlow
@abdulsametjo5z that's a pretty compelling use-case! If you are working on a web project, the agent should be able to preview UI it built with the built in web browser!
Curious how you would envision the UX to be inside of Campus for this.
FlutterFlow
@abdulsametjo5z thanks for the suggestion, Abdulsamet!
Campus feels most useful if it keeps the context handoff map, not just the tools, in one place.
When I run Claude/Codex alongside normal dev work, the hard part is usually returning later and knowing: what did the agent inspect, what assumption did it make, which terminal state mattered, and what still needs a human review.
If Campus can make that history easy for a teammate or future-me to scan, that is a stronger workflow win than simply having fewer tabs open.
FlutterFlow
@grace_lee26 totally - that's the goal. Give it a try and let us know what you think!
FlutterFlow
@grace_lee26 totally agree. The biggest bottleneck right now is context switching.
We're actively optimizing Campus to be equally easy to use for a human & an AI!
FlutterFlow
@grace_lee26 future-me matters SO. MUCH.
FlutterFlow
@ridhwikvinod this is a great question! i'm a growth lead so i know what you mean hehe
we're still in alpha, but i've found that i really love to use Campus to see what my team is building in real-time and actually build my marketing campaigns that way. so instead of having product and marketing separated in silos, there's a more unified sense of vision (and PROGRESS UPDATES)
FlutterFlow
@ridhwikvinod @lydia_lee3 to add to this. In this very first release Campus definitely is more optimized for the developer archetype, just because that's how we're mostly using it.
The bigger vision (and future update will reflect this) is to better support any possible workflow!
FlutterFlow
@ridhwikvinod love this question! We initially built Campus for ourselves to make it as low friction as possible to manage our work, which also means keeping the technical barrier low. So as long as you're building with agents and want your team and other agents to share context, there's nothing stopping your whole team!
the persistent context part is what gets me. losing where an agent left off between sessions is the single most annoying thing about building with them right now
FlutterFlow
@alex_watson2110 agreed! We're entering an area where instead of asking 'how can we observe agents better?' we can start asking ourselves 'how can agents better surface information for us?'.
We believe an interactive canvas is a remarkable good surface for this! More exciting stuff coming soon 👀
@alex_watson2110 this ^^^ the persistent context changes everything
FlutterFlow
@alex_watson2110 @haley_hughes +1 to that
FlutterFlow
@alex_watson2110 yes! It felt like we were banging our heads against a wall before this
Blockem Profiles
Love seeing products focused on reducing context switching. Looking forward to trying this with a team project and seeing how the shared agents fit into the workflow.
FlutterFlow
@angelaa that's what I really love about it - everything in one place. Let us know what you think!
FlutterFlow
@angelaaa thanks, Angela! It's been huge for us, so looking forward to hearing your feedback!
Pretty neat watching this evolve from a real problem for our team into something people can actually use. Excited to see where folks take it from here.
FlutterFlow
@chris_at_flutterflow best products are built out of your own need!
AISA AI Skills Test
the context-switching problem is real, especially when you've got agents running across different tools that don't share state. curious whether Campus handles agent-to-agent handoffs — like when one agent's output needs to feed into another's context without manual copy-paste.
FlutterFlow
@ozandag Campus is built to be a sandbox. Every tile has a dedicated API for the agent to interact with. If you want agents to collaborate, just tell them! They will be able to figure out the details :)
FlutterFlow
@ozandag let us know if you have any other questions!