StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles
Communications plugin

Local Agent Chat

StackOS local conversation surface for direct human-to-agent messages, rich response blocks, and interaction events.

0 listed actions0 capability groups

Connection facts

What the Local Agent Chat connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
No external account required
Setup
Local agent chat stores messages and interactions in StackOS resources; the agent runner owns model invocation and decisions.
Capability groups
No callable capability groups published yet.
Action boundaries
No callable actions published yet.

Action catalog

Actions listed for Local Agent Chat.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

This provider is available to the plugin, but it does not publish callable actions yet.

Direct answer

How does the Local Agent Chat integration work?

People continue using Local Agent Chat as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Local Agent ChatDoes its bounded part
  4. 04Checked resultKeeps the proof

More from Communications

Related integrations.

See the plugin →

Common questions

Local Agent Chat and StackOS.

What can the Local Agent Chat integration do in StackOS?

The current catalog includes the Local Agent Chat provider through the Communications plugin. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Local Agent Chat?

No. Local Agent Chat remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.