Glaze by Raycast. Desktop apps, reimagined by you.

What

Glaze by Raycast is an AI-based app builder for desktop software, starting with Mac. It lets people describe an app in plain language and generate a working desktop app that runs locally on their machine, with access to operating system features such as files, keyboard shortcuts, menu bar behavior, and background processes.

The product appears aimed at individual builders, existing Raycast users, and teams that need internal tools, personal utilities, workflow automations, or lightweight desktop apps without a traditional development process. Its positioning is distinct from browser-focused AI app builders: Glaze emphasizes local-first execution, OS-level access, and desktop-native workflows rather than web deployment.

Features

• Natural-language app creation — Users can describe what they want in plain English and iteratively refine the app by chatting with AI instead of writing all code manually.
• Local-first runtime — Apps run on the user’s machine without requiring a server or internet connection, which supports offline use and keeps app data local.
• OS-level access — Generated apps can work with files, keyboard shortcuts, menu bar elements, background processes, and other desktop capabilities that web apps typically cannot reach.
• Tool and API connectivity — Apps can connect to APIs, local files, hardware, existing tools, and AI models, which broadens the range of workflows they can support.
• Publishing and sharing — Builders can share apps with a team or release them publicly, supporting both internal software distribution and broader discovery.
• Team and community app discovery — Users can explore and install apps from their team and from a wider builder community, suggesting a store-like distribution model.

Helpful Tips

• Assess desktop fit first — This kind of product is most useful when the workflow needs local files, OS automation, menu bar presence, shortcuts, or background execution rather than a browser-only interface.
• Start with narrow internal use cases — Teams will usually get faster value from simple utilities, process helpers, and one-step automations before attempting larger operational software.
• Validate governance needs early — If teams plan to share apps privately, they should clarify review, maintenance, access control, and update ownership even if the page does not detail those controls.
• Check platform alignment — The current focus is Mac, so organizations with mixed-device environments should confirm whether that fits current deployment needs.
• Use coding flexibility selectively — Non-technical users can rely on prompting, while technical users may want to shape or extend outputs further; the exact depth of developer control is not fully described on the page.

OpenClaw Skills

Glaze could likely pair well with OpenClaw as a desktop workflow layer for AI-driven operations. A likely use case would be OpenClaw skills that help users specify internal tools, generate repeatable desktop utilities, and coordinate workflows that combine local files, APIs, and task-specific AI behavior. In practice, that could include agent-led app scaffolding for research utilities, internal dashboards, file-processing helpers, menu bar assistants, or personal productivity tools.

For teams, this combination could shift how non-technical and semi-technical operators create software around daily work. A likely OpenClaw workflow would capture a business need, translate it into a Glaze app spec, manage refinement prompts, and document rollout steps for team distribution. If supported operationally, that could reduce the gap between operational teams and software creation, especially in functions like operations, support, finance, and knowledge work that often need lightweight tools more than full custom platforms.