Skip to content
GOCUX
Documentation
GOCUX / Documentationintegrations

Connect a local agent extension

Let a local extension own its tool and permission loop.

Let a local extension own its tool and permission loop.

Practical procedure

  1. Identify which extension behavior needs a model answer and which behavior executes a local tool.
  2. Route model turns through an authorized supported chat client while keeping local permissions in the extension.
  3. Return tool observations as data and inspect proposed file or network changes before applying them.

Separate the external system from GoCux authority

A named external tool in a workflow does not establish a native GoCux integration. Start with an authorized export, an already configured connector, or a separately implemented adapter. Keep external account credentials in the owning system. In GoCux, inspect the available connector and its grants; the fact that a connector is registered does not itself authorize a task to use it.

Contract example

Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.

GET /connectors — inspect connectors available to the authenticated company

GET /connectors/{connector_id}
GET /connector-defaults
GET /task-contexts/{context_id}/connectors

Inspect the result

The useful outcome is an explicit boundary: what information enters GoCux, which task can access it, and what result leaves. Start with a read-only sample and verify its source context. A local client or adapter owns the external invocation and its error handling unless an actual deployed connector provides that behavior.

What to keep explicit

An extension adapter needs its own implementation and validation. A documentation topic does not establish an installable GoCux extension package.

Handle incomplete and refused work

Authentication with the external system is separate from GoCux authentication. Missing grants, revoked permissions or unavailable connectors must remain visible; do not replace them with invented data. Publishing a marketplace listing, creating a paid external resource or sending messages is a separate action from preparing an integration guide.

Bring this workflow into your workspace.

Set the scope. Review the evidence. Approve the steps that need it.

Open the workspace

Keep exploring