Connections

External systems,
approved and reviewable.

A Connection declares what a Department may reach, how it is resolved by the host, and which actions are permitted. The host owns execution; SpielOS owns the rule.

Apply — Free Review

What a Connection is.

A declared logical connection between a Department and an external system, with credentials and permitted actions.

  • Host-first: OpenCode or Codex resolves the call
  • Declares the external system and purpose
  • Stores credentials in the local env file
  • Direct API use only when truly unattended
  • Keeps every action reviewable
  • Backs outbound, analytics, SEO, and publishing

Exactly how it runs here.

Connections give Departments approved access to outside systems. Buffer supports approved publishing, while PostHog and Search Console provide analytics and SEO evidence; credentials stay private.

How a Connection works.

  1. 1

    Declare the connection with its host resolution and purpose

  2. 2

    Store credentials in the local env file

  3. 3

    Reference it from a Department workflow step

  4. 4

    Resolve the call through the host with the permitted actions

  5. 5

    Record the action in the run evidence

Want this discipline in your company?

The Agent Brief maps one of your workflows to the same loop, approvals, and evidence.

Apply — Free Review