Skip to content

Social Terminal overview

Social Terminal 1.21.0 / Overview

Social Terminal overview

Understand what Social Terminal provides, what Core owns, and when to install an addon.

Social Terminal

Cointacted Social Terminal adds a command-driven interface to WordPress. It owns the terminal UI, command discovery and execution lifecycle, permissions, history, cancellation, and the integration contracts used by official Cointacted addons.

Core is free. You can install it from WordPress.org and run the built-in terminal without buying a license. Addons extend the commands, data sources, publishing destinations, or automation available to the terminal. Each addon documents its own Free and Pro boundary.

What Core includes

  • A responsive terminal for signed-in or public use, according to the access policy you choose.
  • A command registry with help, argument validation, permission checks, and predictable error handling.
  • Request cancellation and protection against stale responses overwriting newer results.
  • Per-user command history where the active access policy permits it.
  • A WordPress administration screen for terminal behavior, access, appearance, and diagnostics.
  • The Add-ons screen for discovering installed products and connecting valid paid access.
  • Provider-neutral integration contracts for SnapWeb, FluentCommunity, MCP, AI, search, blockchain, gamification, and future official addons.

Core does not contain provider-specific blockchain execution, third-party community data, AI-provider credentials, or ecommerce logic. Those responsibilities stay in their owning addons.

Where the terminal can appear

The default terminal works on a normal WordPress page. Install the appropriate bridge when the same terminal must participate in another application shell:

  • Cointacted SnapWeb Free places the core terminal inside the SnapWeb App. Its Pro capability allows supported Cointacted addon surfaces to participate in that SPA.
  • Cointacted FluentCommunity Free registers the core terminal as a native FluentCommunity route. Its Pro capability admits supported Cointacted addon integrations into that portal.
  • Cointacted Shortcodes maps explicitly approved WordPress shortcodes to terminal commands. It is Free-only.

The bridge controls where an addon may run; it does not grant that addon's own Pro features. Both capabilities are checked independently.

Addons and paid access

Open Cointacted → Add-ons to see installed products, available packages, update state, and access status. Free products install and update without a paid license. A paid capability can come from an exact manual license, a connected ShopiChain customer account, or an administrator-issued managed-site grant.

Runtime access is resolved from signed, locally cached entitlement data. Frontend requests do not contact the licensing authority on every page load. If paid access expires or cannot be verified, Pro operations fail closed without deleting settings, content, or customer data.

The Plugins screen uses the same action order for Cointacted products: Settings, Add-ons, then Deactivate. Settings always opens the owning product's administration screen.

Security model

Every command owns its permission and input rules. A command registered for administrators does not become public merely because the terminal itself is visible. Remote execution through MCP or another bridge requires a separately reviewed remote-safety declaration and remains subject to the same WordPress identity and capability checks.

Secrets belong in the owning provider's protected configuration. The terminal should never print private keys, passwords, license secrets, authentication tokens, or raw provider credentials.

  1. Follow Installation and activate Core.
  2. Create or select the WordPress page that will host the terminal.
  3. Configure access before publishing that page in navigation.
  4. Run the built-in help and status commands as an administrator.
  5. Add only the integrations required by the site.
  6. Follow the administrator guide for daily operation, troubleshooting, and data boundaries.
Was this documentation helpful?Your response helps us improve this page.