I assume there is an extensive set of rails for the agent to tie into. (Compare this to asking Claude to green fields an app. Do you use electron? How are notifications handled? Icons? Permissions?)
It springboard off Raycast’s teams feature so well it actually gives it a real reason to exist. You’re empowering the one systems thinker in the group to export their automations to the rest of the group in a way that’s proven to work: small apps that do one thing. (Big apps get complicated, become full time projects that distract from the task at hand)
Fig tried this but it was just for engineers, the value prop was missing, Glaze seems to get this right.
I assume there is an extensive set of rails for the agent to tie into. (Compare this to asking Claude to green fields an app. Do you use electron? How are notifications handled? Icons? Permissions?)
It springboard off Raycast’s teams feature so well it actually gives it a real reason to exist. You’re empowering the one systems thinker in the group to export their automations to the rest of the group in a way that’s proven to work: small apps that do one thing. (Big apps get complicated, become full time projects that distract from the task at hand)
Fig tried this but it was just for engineers, the value prop was missing, Glaze seems to get this right.
Very nicely done!