change assistants to ai apps

Author: haleychaas

docs/content/concepts/assistant.md docs/content/concepts/ai-apps.md

@@ -1,18 +1,18 @@
 ---
-title: Agents & Assistants
+title: AI Apps
 lang: en
-slug: /concepts/assistant
+slug: /concepts/ai-apps
 ---
 
 :::info[This feature requires a paid plan]
 If you don't have a paid workspace for development, you can join the [Developer Program](https://api.slack.com/developer-program) and provision a sandbox with access to all Slack features for free.
 :::
 
-Agents and assistants comprise a new messaging experience for Slack. If you're unfamiliar with using agents and assistants within Slack, you'll want to read the [API documentation on the subject](https://api.slack.com/docs/apps/ai). Then come back here to implement them with Bolt!
+AI apps comprise a new messaging experience for Slack. If you're unfamiliar with using AI apps within Slack, you'll want to read the [API documentation on the subject](https://api.slack.com/docs/apps/ai). Then come back here to implement them with Bolt!
 
-## Configuring your app to support assistants 
+## Configuring your app to support AI features
 
-1. Within [App Settings](https://api.slack.com/apps), enable the **Agents & Assistants** feature.
+1. Within [App Settings](https://api.slack.com/apps), enable the **Agents & AI Apps** feature.
 
 2. Within the App Settings **OAuth & Permissions** page, add the following scopes: 
   * [`assistant:write`](https://api.slack.com/scopes/assistant:write)
@@ -25,12 +25,12 @@ Agents and assistants comprise a new messaging experience for Slack. If you're u
   * [`message.im`](https://api.slack.com/events/message.im)
 
 :::info
-You _could_ implement your own assistants by [listening](/concepts/event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events. That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
+You _could_ implement your own AI app by [listening](/concepts/event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events. That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
 :::
 
 ## The `Assistant` class instance
 
-The [`Assistant`](/reference#the-assistantconfig-configuration-object) can be used to handle the incoming events expected from a user interacting with an assistant in Slack. A typical flow would look like:
+The [`Assistant`](/reference#the-assistantconfig-configuration-object) can be used to handle the incoming events expected from a user interacting with an AI app in Slack. A typical flow would look like:
 
 1. [The user starts a thread](#handling-new-thread). The `Assistant` class handles the incoming [`assistant_thread_started`](https://api.slack.com/events/assistant_thread_started) event.
 2. [The thread context may change at any point](#handling-thread-context-changes). The `Assistant` class can handle any incoming [`assistant_thread_context_changed`](https://api.slack.com/events/assistant_thread_context_changed) events. The class also provides a default `context` store to keep track of thread context changes as the user moves through Slack.
@@ -52,17 +52,17 @@ const assistant = new Assistant({
 });
 ```
 
-While the `assistant_thread_started` and `assistant_thread_context_changed` events do provide Slack-client thread context information, the `message.im` event does not. Any subsequent user message events won't contain thread context data. For that reason, Bolt not only provides a way to store thread context — the `threadContextStore` property — but it also provides a `DefaultThreadContextStore` instance that is utilized by default. This implementation relies on storing and retrieving [message metadata](https://api.slack.com/metadata/using) as the user interacts with the assistant. 
+While the `assistant_thread_started` and `assistant_thread_context_changed` events do provide Slack-client thread context information, the `message.im` event does not. Any subsequent user message events won't contain thread context data. For that reason, Bolt not only provides a way to store thread context — the `threadContextStore` property — but it also provides a `DefaultThreadContextStore` instance that is utilized by default. This implementation relies on storing and retrieving [message metadata](https://api.slack.com/metadata/using) as the user interacts with the app. 
 
 If you do provide your own `threadContextStore` property, it must feature `get` and `save` methods.
 
 :::tip
-Be sure to give the [assistants reference docs](/reference#agents--assistants) a look!
+Be sure to give the [AI apps reference docs](/reference#agents--assistants) a look!
 :::
 
 ## Handling a new thread {#handling-new-thread}
 
-When the user opens a new thread with your assistant, the [`assistant_thread_started`](https://api.slack.com/events/assistant_thread_started) event will be sent to your app. Capture this with the `threadStarted` handler to allow your app to respond. 
+When the user opens a new thread with your AI app, the [`assistant_thread_started`](https://api.slack.com/events/assistant_thread_started) event will be sent to your app. Capture this with the `threadStarted` handler to allow your app to respond. 
 
 In the example below, the app is sending a message — containing thread context [message metadata](https://api.slack.com/metadata/using) behind the scenes — to the user, along with a single [prompt](https://api.slack.com/methods/assistant.threads.setSuggestedPrompts).
 
@@ -85,7 +85,7 @@ In the example below, the app is sending a message — containing thread context
 ```
 
 :::tip
-When a user opens an assistant thread while in a channel, the channel info is stored as the thread's `AssistantThreadContext` data. You can grab that info using the `getThreadContext()` utility, as subsequent user message event payloads won't include the channel info. 
+When a user opens an AI app thread while in a channel, the channel info is stored as the thread's `AssistantThreadContext` data. You can grab that info using the `getThreadContext()` utility, as subsequent user message event payloads won't include the channel info. 
 :::
 
 ## Handling thread context changes {#handling-thread-context-changes}
@@ -100,13 +100,13 @@ When the user switches channels, the [`assistant_thread_context_changed`](https:
 ...
 ```
 
-If you use the built-in `AssistantThreadContextStore` without any custom configuration, you can skip this — the updated thread context data is automatically saved as [message metadata](https://api.slack.com/metadata/using) on the first reply from the assistant bot.
+If you use the built-in `AssistantThreadContextStore` without any custom configuration, you can skip this — the updated thread context data is automatically saved as [message metadata](https://api.slack.com/metadata/using) on the first reply from the app.
 
 ## Handling the user response {#handling-user-response}
 
-When the user messages your assistant, the [`message.im`](https://api.slack.com/events/message.im) event will be sent to your app. Capture this with the `userMessage` handler. 
+When the user messages your AI app, the [`message.im`](https://api.slack.com/events/message.im) event will be sent to your app. Capture this with the `userMessage` handler. 
 
-Messages sent to the assistant do not contain a [subtype](https://api.slack.com/events/message#subtypes) and must be deduced based on their shape and any provided [message metadata](https://api.slack.com/metadata/using).
+Messages sent to the app do not contain a [subtype](https://api.slack.com/events/message#subtypes) and must be deduced based on their shape and any provided [message metadata](https://api.slack.com/metadata/using).
 
 There are three [utilities](/reference#the-assistantconfig-configuration-object) that are particularly useful in curating the user experience:
 * `say`

docs/docusaurus.config.js

@@ -69,6 +69,10 @@ const config = {
             to: '/',
             from: ['/concepts', '/concepts/advanced', '/concepts/basic'],
           },
+          {
+            to: '/concepts/ai-apps',
+            from: '/concepts/assistant'
+          }
         ],
       },
     ],

docs/sidebars.js

@@ -39,7 +39,7 @@ const sidebars = {
             'concepts/publishing-views',
           ],
         },
-        'concepts/assistant',
+        'concepts/ai-apps',
         'concepts/custom-steps',
         {
           type: 'category',