How Teams use Glaze

What teams are building with Glaze

We built Glaze so anyone can be a toolmaker. Since opening the beta, we've been blown away with what people are building, but what stood out was how helpful Glaze is to build internal tools within teams. Whether it's an idea that you've had in your head for years or an app that solves a friction point throughout your daily workflow, with just a few prompts that app can become a reality.

---

Quinn at Linear: A CX hub that lives in the menu bar

Quinn leads support at Linear and was about to be away for nearly two months. Before this, the team would check their queue directly in Intercom: reactive, not proactive. No easy way to spot a spike forming, correlate a customer report with a recent deploy, or know who was on-call without switching to another tool. Each of those was its own context switch.

So Quinn built a CX Hub. It connects to Intercom to show live queue counts and surface volume trends. It pulls from a Slack channel of GitHub deploy notifications and summarizes recent commits in plain English, so if customers start reporting something broken, the team can see at a glance what recently shipped that might have caused it. It shows on-call information and the status pages for services Linear depends on, so if a provider has an outage that's affecting customers, the answer is right there. It fires desktop notifications when a ticket is urgent or volume crosses a threshold. And it lives in the menu bar with a live counter, always visible, one glance away.

What started as a handoff tool before a trip became the team's everyday setup. A few days after it went live:

"It actually helped me early detect an incident yesterday. My computer started pinging like crazy whilst I was in another room and I heard it." — Quinn, Support team at Linear

---

Florentin at Vercel: A PR tracker that lives in the menu bar

Florentin is a software engineer at Vercel working across multiple repos. Checking on PRs meant switching to the browser, navigating to the right view, and remembering what was pending. Small overhead, but it adds up.

So Florentin built a menu bar app that wraps the GitHub CLI. It shows open PRs, drafts, CI status, review assignments, and diff sizes, all in one panel, one click away from anywhere on the desktop. From there he can jump directly to a failing action and restart it, approve a rollout, or read through comments without leaving the app. Which repos are shown, which users and teams are tracked for review requests: all configurable.

"Menu bar app that is a GitHub CLI wrapper so I can see my PRs / action run status / review assignments." — Florentin, Vercel

A Raycast extension could have done something similar. Florentin chose Glaze for the control it gave over how the UI looks. The app is exactly what he wanted it to be, visually and functionally.

No browser. No context switch. Just the current state of everything that needs attention.

---

Tarun at Cursor: A screenshot app with no friction

When Tarun at Cursor was setting up a new work Mac, the screenshot app he used was no longer on the store. He could have moved it between machines, but it had always had an annoying step: you had to manually click a checkmark to save or copy. A small thing, but a daily one.

He built a SnapClip in a few prompts. Exactly the behavior he wanted, nothing else. He published it to the Glaze store for his team. The first time he needed to report a bug, he used the app he'd just made to capture the screenshot.

"I could have just moved the app between my machines, but it had a few frictions. Glaze happened at the right time, so I just few-shotted it." — Tarun Kumar, Cursor

---

Quinn's app is connected to half a dozen APIs. Florentin's collapses a GitHub workflow into a menu bar. Tarun's is a screenshot tool built in one afternoon. They're completely different, but each one started the same way. Someone had a specific need and built exactly what they needed.

Stop searching for the perfect tool. Start making it. Try Glaze →