ChatFolders vs Glean Actions

“The cross-platform angle is what makes this actually useful. I use different models for different tasks — Claude for writing, ChatGPT for code, Gemini for research — and having one organizational system that works across all of them without switching contexts is a genuine quality-of-life improvement. Local-first is also the right call for professional conversations.”

“The primitive here is: natural language → workflow action dispatch, using Glean's existing knowledge graph as the intent resolver. That's a defensible idea. But the entire blog post is marketing copy with a screenshot at the bottom — there's no API surface documented, no SDK, no mention of how custom actions are defined or what the action schema looks like. If I'm an IT engineer at a 5,000-person company who wants to add a custom action for our in-house provisioning tool, I have no idea how to do that from anything published. The DX bet is entirely opaque, and a tool that lives inside enterprise deals with no developer-facing documentation is a platform I have to adopt wholesale on someone else's timeline — exactly what I'm tired of.”

“Browser extensions for major AI platforms are inherently fragile — one UI update from OpenAI or Anthropic breaks everything until the solo developer finds time to patch it. The local-only storage also means your organizational system doesn't follow you to a new computer. This solves a real problem but in a brittle, unscalable way.”

“Glean already owns the search index in enterprises where it's deployed, so Actions isn't a cold-start problem — it's an upsell on top of data access they already have. The direct competitors are ServiceNow's AI layer, Microsoft Copilot for M365, and frankly just Slack + a well-configured Workato flow. Where this breaks: any company whose HR and IT data isn't cleanly indexed in Glean already, which is most companies in year one of a Glean deployment. My 12-month prediction: this either becomes table stakes for Glean's renewal motion or it gets cannibalized when Microsoft ships the same workflow triggers natively in Copilot Studio — Glean's bet is that enterprise search context beats platform incumbency, and that's a real but narrow window.”

“The fact that someone had to build this as a browser extension is the real story: none of the major AI companies have prioritized knowledge management for power users. ChatFolders is filling a gap that should have been filled by product teams months ago. Either someone acqui-hires this developer, or the major platforms ship native folder systems within the year.”

“For content creators juggling project briefs, brand voice docs, and campaign conversations across multiple AI tools, this is genuinely useful. Color-coded folders alone is worth the install — visual organization of a chaotic sidebar has an immediate quality-of-life impact. The auto-sort rules could save hours per week for heavy users.”

“The buyer is the CIO or CHRO who already wrote a Glean check — this is pure expansion revenue with essentially zero new sales motion required, which is a beautiful thing. The moat is the existing index: once Glean has crawled your Workday, ServiceNow, and Confluence, the switching cost to rip it out and replace it with Copilot is genuinely painful. The risk is that this is an enterprise feature expansion masquerading as a product launch — if it's gated behind an additional SKU with a separate SOW negotiation, adoption will be slow enough that competitors close the gap before Glean gets the case studies.”

“The job-to-be-done is clear and singular: let an employee resolve an HR or IT need without opening a new tab or filing a ticket manually. That's a real, high-frequency frustration in any company over 500 people, and Glean is solving it at the right layer — the search interface where employees already go to find answers. The completeness question is the real test: this only works if your company's Glean deployment is mature, your HR and IT data is actually indexed and current, and your IT team has configured the action integrations. For a new Glean customer, this is a 6-month-away feature, not a day-one capability — which means it's a retention play, not an acquisition hook. Still a ship because the job is real and the placement is right.”