Skip to content

AssistedDevtools

AssistedDevtools lends nothing. It mounts assistant-ui’s devtools with an Assisted pages tab that shows what the open page lends, as the next turn will send it.

The devtools window on Orders with the Assisted pages tab open: the page's name, the note the next turn sends, and get_page_content's answer.The devtools window on Orders with the Assisted pages tab open: the page's name, the note the next turn sends, and get_page_content's answer.

Import it from the devtools entry and render it inside AssistedProvider. From examples/app/app/assistant.tsx:

import { AssistedDevtools } from "@super-assist/react/devtools";
<AssistedProvider
runtime={runtime}
destinations={destinations}
navigate={(path) => router.push(withMode(path))}
>
<Layout>{children}</Layout>
<AssistedDevtools />
</AssistedProvider>

The launcher sits in the bottom-right corner in development. DevToolsModal renders nothing in production builds.

Nothing from the devtools. The tab shows what the other components lend: the open page’s note under Note the next turn sends, what get_page_content answers now, and every lent tool with its description. It re-reads every second.

The Assisted pages tab on Settings, scrolled to Actions and Fields: save_settings with a ring chip, the setting field tool with its ids and what each field says now, then the page and global tools.The Assisted pages tab on Settings, scrolled to Actions and Fields: save_settings with a ring chip, the setting field tool with its ids and what each field says now, then the page and global tools.

On Settings, save_settings carries a ring chip read from its marker, and the setting field tool lists its ids and what each field says now. The devtools reference lists every section of the tab.

None. To add the tab to a DevToolsModal of your own, pass assistedPagesPlugin from the same entry, as the devtools reference describes.