Slate Co-Captain

🏔️ Summit 2026 Feature

Let Slate AI inspect and work through Slate pages with a supervised Co-Captain browser session.

Slate Co-Captain extends Slate AI from answering questions to acting in the current Slate page under user supervision. After a user confirms the session, Co-Captain can navigate Slate, open dialogs, click, scroll, type, review page content, and return a summary of what it found or changed.

You can use Co-Captain when a task depends on the current page context and would otherwise require several manual clicks to inspect, verify, or adjust configuration. For example, Co-Captain can inspect a form builder page, open field settings, check whether fields are required, and return a table of results.

How Co-Captain works

Co-Captain works from the Slate AI side panel. The user enters a prompt, Slate AI explains that the request will use Co-Captain, and the user confirms whether the browser-control session should begin. This confirmation step helps prevent Co-Captain from acting before the user has reviewed the request.

After confirmation, Slate opens a Co-Captain window that shows the session in progress. The Slate AI side panel continues to display status updates, such as the pages, dialogs, or fields Co-Captain is inspecting. The user can stop the session at any time.

Before you begin

• Open the Slate page where Co-Captain should work.

• Decide whether the request should be read-only or whether Co-Captain may make changes.

• Use a test environment when validating a new prompt, especially if the prompt asks Co-Captain to update configuration.

• Review Co-Captain's actions and final response before relying on the result.

Co-Captain operates in the current user's Slate context. It can work only with pages, records, and actions available to that user.

Starting a Co-Captain session

1. Open the Slate page where Co-Captain should inspect or complete the task.

2. Open the Slate AI side panel.

3. Enter a direct prompt that describes the task and any limits Co-Captain should follow.

4. Review Slate AI's confirmation message.

5. Confirm that Co-Captain should begin the session.

6. Watch the Co-Captain window and the Slate AI status updates while the task runs.

7. Review the final response after the session finishes.

Writing safer prompts

Prompts should tell Co-Captain what to inspect, what outcome to return, and whether it should make changes. For read-only checks, explicitly state that Co-Captain should not save or change anything, as with:

💬 Can you use Co-Captain to inspect this form and tell me whether the visible form fields are marked as required? Please do not save or change anything.

For configuration updates, describe both the change and the review expectation:

💬 Can you use Co-Captain to add a red asterisk to each required field label on this form? Stop before saving if you see any unexpected field settings.

Reviewing a Co-Captain result

After Co-Captain finishes, Slate AI returns a response that summarizes the work completed. Depending on the prompt, the response may include a table, notes about what was inspected, or a description of any changes made.

In a validated test of a form builder page, Co-Captain opened field dialogs, checked the Required for submission setting, closed dialogs without saving, and returned a table showing which visible fields were required.

Stopping or redirecting Co-Captain

Co-Captain is designed for supervised use. Stop the session if Co-Captain begins working on the wrong page, appears to misunderstand the task, or starts an action that should not continue. After stopping, revise the prompt with clearer scope before starting a new session.

Prompt examples

• Audit an application: Ask Co-Captain to inspect an application form and report which required fields are missing a visible indicator for applicants.

• Inspect a form: Ask Co-Captain to identify which visible fields in an advising form are required and return the results in a table.

• Review a query: Ask Co-Captain to open query settings and summarize the exports, filters, and sorts without saving changes.

• Check a configuration page: Ask Co-Captain to confirm whether a setting is enabled and explain where it found the setting.

• Make a small update: Ask Co-Captain to complete a specific edit, then summarize exactly what changed.