Shane Buchan

What if your background agents could be foreground agents? I recently shipped a new version of our "Projects" feature in Glass, @tryramp's internal AI productivity tool, that maintains per-project memory across chat sessions. This allows each chat session to have full awareness of what all other sessions, past or present, are doing in a project. Our users no longer have to worry about running out of context. They can seamlessly stop one session and spin up another with the prompt "Continue" and the agent will know exactly what to do. We're also now able to explore fun ideas like loading every background agent from a parent session as their own individual chat session within a single view so you can see every tool call a child session makes or interrupt/manage them independently. Check out the video to see it in action👇

@otc_slaps @tryramp All in Glass 😁

@buchan_sm @tryramp How did they do it? In glass or did you tell them to do it in Claude code and report back? Or what? lol

We held a company-wide AI hackathon at @tryramp and got to put Glass, our internal AI productivity app, to the test. 650 participants. 100 AI mentors. 305 submissions. 7 finalists. 1 Glass. It was a blast getting to see so many non-engineers become builders and bring their ideas to life as full featured internal apps or robust, shareable skills.

I couldn’t agree more. There’s so many problems to solve out there that engineers like myself would never even be able to think up let alone find solutions for. It makes perfect sense to give folks in Sales, CX, Marketing, etc. the tooling to solve the problems they run into each day on their own. No one will understand their problem better than they will.

@buchan_sm @tryramp AI hackathons get more interesting when non engineers can build something real instead of just prompting around the edges. Internal tools like Glass seem valuable mainly because they compress the path from idea to usable workflow.

@ironcarbs @getopenwork It was huge, tbh. Allowing folks to conveniently use Okta SSO for every MCP, eliminated a pretty big UX frustration and made it that much easier for folks to adopt Glass internally.

@buchan_sm This was a really interesting read. Thanks for the level of detail on Ramp's Dojo. Very much aligned regarding enabling non-technical people to contribute. We've built the SkillsHub with a very similar mindset at @getopenwork. How much of an unlock was it to aggregate MCPs?

Last week @sebgoddijn shared Glass, Ramp's internal AI productivity tool, with the world. Nearly a million views later, everyone's asking the same thing: how did you actually build this? Read the full story here: x.com/buchan_sm/stat… The short of it: we built an app that builds itself A small team of us pretty much vibe coded the entire thing in about a month. The trick was teaching Glass how to improve its own codebase. Turns out if you discipline your AI agents well enough, they grow up to be high-functioning, self-sufficient adults in no time.