Managing Agents
How an App is translated to an Agent
When migrating from Apps to Agents, each App component maps directly to its Agent equivalent to ensure seamless functionality.
Building blocks of an AI Application:
-
Name
- App Display Name → Agent Name
- Direct one-to-one mapping with no changes
-
Icon
- App Icon → Agent Icon
- Visual representation remains identical
-
Description
- App Description → Agent Description
-
Instructions
- App Instructions → Instructions for the “Plan & Execute” step in the Agent (see screenshot below)
-
Actions
- App Actions → Actions for the “Plan & Execute” step in the Agent
- All configured actions and their customization are preserved as-is.
Additional Migration Details:
- Permissions & Access:
- App library audience (Users, Departments) → Agent VIEWER roles
- App Editors → Agent EDITOR roles
- Creator becomes Agent Owner
- Configuration:
- Prompts → Converted to conversation starters for the agent.
- Integration:
- Slack Settings are preserved as-is and can be accessed from the “Share menu” in the Agent builder.
ℹ️ The migrated agent will refer to itself asAgent: <name>in Slack in its responses instead ofApp: <name>.
- Slack Settings are preserved as-is and can be accessed from the “Share menu” in the Agent builder.
Example: Sample Agent (migrated from an App)
FAQs
FAQs
[Q] What happens to bookmarked links to my Application post-migration, such as https://app.glean.com/chat?applicationId=example_application ?
- Once the migration is completed, Glean will seamlessly redirect any navigation from a link to an App to the corresponding Agent, so any previously bookmarked links for Apps will continue to work.
[Q] What about the Web SDK? I’m using an App with chat embedded on my website.
- Currently, one can embed an AI App in their site by using the applicationId parameter such as:
- Post-migration, your existing code that is using applicationId with the Web SDK will continue to work as Glean internally translates the applicationId to the corresponding migrated agentId, ensuring your embedded chat functionality remains uninterrupted.
Note:
Note:
- The applicationId parameter will not work for new agents, and agentId should be used instead.
- We recommend switching to agentId for Web SDK usage of migrated agents once the same is completed.
[Q] I’m using the App via REST API, will the app stop working when called via /rest/api/v1/chat?
- For Apps that are migrated to an Agent, Glean will internally translate the applicationId parameter in the chat request to the corresponding agentId to ensure functionality remains uninterrupted.
Note:
Note:
- The applicationId parameter will not work for new agents, and agentId should be used instead.
- We recommend switching to agentId for REST API usage of migrated agents once the same is completed.
[Q] Will my App’s conversation history be preserved?
- Yes, all existing chat sessions and conversation history will be maintained.
[Q] What happens to my App’s Slack integration?
- Your App’s Slack settings and channel mappings will transfer directly to the corresponding Agent. The Agent will maintain the same Slack functionality and channel associations as your original App.
[Q] Can I continue using my App during the migration process?
- During the migration phases, your Apps will continue to function normally until it is successful and they are replaced with the corresponding agent.
[Q] What if I made changes to my App before migration?
- Any changes made to Apps before the final migration will be preserved in the resulting Agent.