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.
Hey Product Hunt! Alex here, co-founder of FlutterFlow.
Not long ago, I used to have 20+ terminal tabs open, each connected to a different part of my projects. Claude in one. Codex in another. Browser tabs, docs, notes, Git worktrees, design files, all scattered across different windows. Every time I switched tasks, I had to remember where everything was and rebuild context.
It got even harder because we're a remote team. I wanted to share context, get feedback, and see what everyone was working on without scheduling another meeting or asking someone to share their screen.
So we built Campus.
Campus gives every project its own persistent workspace. Instead of jumping between apps, everything lives together on one canvas: terminals, browsers, documents, designs, files, AI agents, and most importantly your teammates. When you come back tomorrow or someone new joins the project, the context is already there.
Today our entire team builds in Campus every day, and it's completely changed how we work together. My favorite part is the sense of connection - we’re dropping GIF reactions, memes, and screenshots into the canvas mid-build.
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!
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?
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!
@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.
@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?
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?
I can see this working really well as an individual, but it feels a little big brothery to do this as a team.
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.
Congrats on the launch! The humans-plus-agents handoff is the part I always find hardest, knowing when an agent should stop and pull a person in vs keep going. Curious how Campus draws that line. Looks slick.
Congrats on the launch! Since terminals and agents live on this shared canvas, if I close my laptop mid-task, does the agent keep running in the background, or does everything just pause until I'm back?
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.
The one-click deploy to app stores and web is the detail that jumps out — most tools get you to a pretty prototype and then leave you stranded at the "now actually ship it" cliff. Keeping it fully extensible with custom code is the right call too; the no-code tools that trap you the moment you need something custom always lose me. Curious where the generated code lands on the clean-vs-just-works spectrum, since that's usually where these tools live or die. Congrats on the launch! 🚀
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?
This looks really compelling. How do agents on the canvas get their context, do they read the full repo, docs and past conversations automatically, or can you scope what each agent is allowed to see and touch (repo vs terminal vs docs)? Curious how you keep multiple agents' work reviewable when they're building alongside the team.
Congrats Alex and team! Everyone in the thread is asking the dev questions, so here’s the other side: I’m the non-technical guy who runs AI agents for marketing and ops at a 36-person company. My context is just as scattered as your 20 terminal tabs, except mine is Slack threads, Sheets, and a dozen Claude chats. Is Campus genuinely usable for someone like me working alongside agents, or is it dev-first for now with terminals and worktrees at the center? The answer decides whether I bring my whole team in or just watch the engineers have fun.
the "one persistent workspace instead of scattering across Slack/docs/tickets" pitch makes sense for the human side, but I'm curious about the agent side specifically - if two different agents (or an agent and a human) are working on the same repo context at the same time, does Campus have any concept of locking or conflict resolution, or is it more like a shared read layer where the actual edits still happen elsewhere and could still collide?
Love to see more connections between human and AI. Wondering whether other messaging tools are also supported as I dont use slack that much. And why do you folks pick slack?
About Campus on Product Hunt
“One project space for humans and AI agents”
Campus launched on Product Hunt on July 15th, 2026 and earned 445 upvotes and 110 comments, earning #3 Product of the Day. 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.
Campus was featured in Productivity (656.2k followers), Software Engineering (42.7k followers) and Developer Tools (515.9k followers) on Product Hunt. Together, these topics include over 229.4k products, making this a competitive space to launch in.
Who hunted Campus?
Campus was hunted by Ben Lang. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Campus stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Ben Lang
Hey Product Hunt! Alex here, co-founder of FlutterFlow.
Not long ago, I used to have 20+ terminal tabs open, each connected to a different part of my projects. Claude in one. Codex in another. Browser tabs, docs, notes, Git worktrees, design files, all scattered across different windows. Every time I switched tasks, I had to remember where everything was and rebuild context.
It got even harder because we're a remote team. I wanted to share context, get feedback, and see what everyone was working on without scheduling another meeting or asking someone to share their screen.
So we built Campus.
Campus gives every project its own persistent workspace. Instead of jumping between apps, everything lives together on one canvas: terminals, browsers, documents, designs, files, AI agents, and most importantly your teammates. When you come back tomorrow or someone new joins the project, the context is already there.
Today our entire team builds in Campus every day, and it's completely changed how we work together. My favorite part is the sense of connection - we’re dropping GIF reactions, memes, and screenshots into the canvas mid-build.
Download Campus and create your first work area: campus.flutterflow.io
Happy to answer anything in the comments.
— Alex, co-founder at FlutterFlow