Pick a topic to dive in and start chatting with peers and Glean employees.
My team has expressed concerns that whenever they execute the agent, the chat history displays the agent's name. After several runs, it becomes challenging to differentiate or filter the outputs from same agent. Does anyone know how to modify this?
Our company is rolling out Glean soon, and I’d love ideas from others in Client Success Operations roles on how to get the most out of it. I’m a Client Success Operations Manager supporting our Client Success teams (Support, Implementation Consultants, Client Success Managers, Technical Account Managers, and Admin…
There are times where you have crafted a sub-agent that fits along different branches within your agent's logic, but currently there's no way to copy that sub-agent and re-use it. Is this a feature customers would like to see? Comment and react for increased visibility
I'm realizing more and more of our employee population uses Google Tasks. I believe it would be pretty valuable if Glean had a way of indexing Tasks along with action that allow users to update their tasks from Glean.
Is this in GA?
We’re building lots of agents, and many share the same tasks (e.g., Project Kickoff & Project Handover Agents both pull Salesforce data). What if we had reusable “Lego block” sub-agents? One agent = block could fetch Salesforce data, another could process Gong calls, etc. We’d save time, avoid duplicate work, and keep…
When documents contain embedded hyperlinks (e.g., text like "click here" linking to a URL), Glean Chat, Agents, and API/MCP only return the visible text - not the actual URL behind it. Users are told to open the source document and click the link manually. This is a poor experience, especially when: Documentation is full…
Hi Glean Community! I wish there was an easy way to allow our end users to categorizes agent they have built instead of having a Glean admin or Agent Moderator do it for them. This creates a lot of administrative overload for a fairly easy task that can be self serviced. We also don't want to allow everyone Agent Moderator…
Can someone explain to me when a search will use the live SOQL query vs pulling from the previously crawled Salesforce data?
Currently enabling Jira JQL integration is a per user setting. Can this be enabled globally so we end users don't have to enable it individually?
Create an Idea post and tag it Feedback and Ideas so the community can upvote and our product team can prioritize it.
