Skip to main content
SINT Console is the operational control center for the SINT ecosystem. It connects to the SINT Protocol gateway via WebSocket (JSON-RPC 2.0) and provides a visual interface for everything: agent management, workflow orchestration, policy enforcement, evidence monitoring, and multi-agent coordination.
Source: github.com/sint-ai/sint-agents — React 19, Redux Toolkit 2.5, 31 feature modules, 110+ test files, 60+ feature flags.

Architecture

┌──────────────────────────────────────────────────────┐
│                    SINT Console                       │
│  ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌─────────┐ │
│  │ Conductor│ │  Canvas   │ │ Operator │ │  Web3   │ │
│  │ (Policy) │ │ (Flows)  │ │ (Tasks)  │ │(Wallet) │ │
│  └────┬─────┘ └────┬─────┘ └────┬─────┘ └────┬────┘ │
│       └─────────────┴────────────┴────────────┘      │
│                         │                             │
│              GatewayDataService                       │
│         (auto: WebSocket → REST → Mock)               │
└─────────────────────────┬─────────────────────────────┘
                          │ JSON-RPC 2.0 / WebSocket
                          │ Ed25519 device identity

              ┌───────────────────────┐
              │  SINT Protocol        │
              │  Policy Gateway       │
              │  (32 REST endpoints)  │
              └───────────────────────┘
The Console uses a cascading data strategy:
  1. Gateway WebSocket — Real-time bidirectional communication (preferred)
  2. REST API — Fallback when WebSocket is unavailable
  3. Mock data — Offline development mode
Authentication uses Ed25519 device identity — the Console generates a keypair on first visit and authenticates via signed nonce challenge.

Core Modules

🎛️ Conductor — Multi-Agent Orchestration

The Conductor is the Console’s primary interface for managing SINT Protocol operations. It maps directly to the gateway’s API surface.

Conductor Dashboard

Real-time overview of active runs, agent status, and system health. Shows running agents, pending approvals, recent evidence events, and risk distribution.Route: /app/conductor

Approval Gates

Human-in-the-loop approval queue for T2+ operations. Operators can approve, deny, or escalate pending agent actions with full context (token details, risk tier, constraint values).Route: /app/conductor/approvals

Policy Editor

Create, edit, toggle, and delete policy rules. Policies define constraints (force limits, velocity caps, geofences) and conditions (agent ID, resource type, action category).Route: /app/conductor/policyAPI: POST/PATCH/DELETE /conductor/policies

Evidence Browser

Browse and filter the SHA-256 hash chain evidence ledger. Filter by run, event type, time range. View chain integrity status and generate proof receipts for audit.Route: /app/conductor/evidence

Goal Monitor

Track active agent goals and monitor for goal hijacking attempts. The goal hijack detector (25+ patterns, 0.6 confidence threshold) surfaces suspicious activity in real-time.Route: /app/conductor/goals

Server Registry

Monitor connected MCP servers, their capabilities, and health status. Register new servers, view tool catalogs, track connection stability.Route: /app/conductor/servers

🖼️ Canvas — Visual Workflow Builder

A drag-and-drop flow editor for composing multi-agent workflows. Built with React Flow (@xyflow/react). 13 node types:
NodePurpose
agentAI agent execution node
taskTask assignment and tracking
conductor_runSINT Protocol governed run
mcp_serverMCP tool server integration
policyPolicy checkpoint / gate
chatChat interaction node
triggerFlow start (manual, webhook, scheduled)
conditionConditional branching (expression evaluation)
outputResult collection / logging
swarmMulti-agent swarm coordination
n8n_workflown8n integration node
Pre-built templates:
TemplateDescription
Social Media PipelineContent generation → review → publish
Market AnalysisData gathering → analysis → report
Research & SummarizeWeb scrape → summarize → output
Multi-Agent ConsensusMultiple agents → voting → decision
RAG: Document IngestionUpload → chunk → embed → store
RAG: Knowledge QueryQuery → retrieve → generate response
NEXUS: Startup MVPIdea → research → prototype → test
The FlowExecutor engine processes flows using topological sort (Kahn’s algorithm), executing nodes in dependency order with real-time status updates. Route: /app/canvas

📊 Operator — Operations Management

Tasks (Kanban)

Task management with Kanban board, status tracking, auto-assignment, checkout locking, and activity logs. Linked to conductor runs for full traceability.Route: /app/operator/tasks

Traces

Execution traces with detailed step-by-step logs, timing data, and gateway message history. Drill into any agent run to see exactly what happened.Route: /app/operator/traces

Sessions

Active session management — view connected agents, session state, message history, and real-time activity.Route: /app/operator/sessions

Memory

Agent memory browser — view shared context, cross-session learning data, and memory entries with importance scoring.Route: /app/operator/memory

🧠 Intelligence

Agent intelligence dashboard with:
  • Activity Feed — Real-time stream of all agent actions
  • Skills Manager — View, configure, and install agent skills
  • Stats Dashboard — Aggregated metrics: actions/hour, success rate, cost/action
  • Trajectory Page — Visualize agent decision paths over time
Route: /app/intelligence

💰 Web3 & Trading

Web3 Dashboard

Multi-chain wallet management (EVM, Solana, Cosmos). Token balances, transaction history, DeFi panel, send/receive modals, and token swap via integrated DEX aggregator.Route: /app/web3

Trading Dashboard

Real-time price feeds (via API integration), interactive charts (lightweight-charts), portfolio tracker, and position management.Route: /app/trading

🏪 Marketplace

Agent marketplace with:
  • MCP server discovery and installation
  • Skill/plugin catalog with filtering
  • Community-contributed templates
  • n8n workflow import
Route: /app/marketplace

📈 Metrics & Observability

  • Metrics Dashboard — System-wide KPIs: latency, throughput, error rates, cost tracking
  • Observability Page — Deep diagnostics, log aggregation, anomaly detection alerts
  • Cost Tracking — Per-agent, per-run cost breakdown with budget alerts and predictions
Routes: /app/metrics, /app/observability

State Management

The Console uses Redux Toolkit 2.5 with 31 operator feature slices:
CategorySlices
OrchestrationconductorSlice, canvasSlice, canvasExecutionSlice
AgentsagentSlice, handoffSlice, sharedContextSlice
TaskstaskSlice, scheduleSlice, templateSlice
GovernanceapprovalSlice, trustPolicySlice, auditSlice
MonitoringmetricsSlice, anomalySlice, runEventSlice, sessionSlice
IntelligenceintelligenceSlice, operatorSlice (traces)
FinancebudgetSlice, tradingSlice, web3Slice
InfranotificationSlice, marketplaceSlice, webhookSlice
All slices follow the same pattern: async thunks → reducers → selectors → tests.

Gateway Integration

The Console connects to SINT Protocol’s gateway server via the GatewayClient — a WebSocket client implementing JSON-RPC 2.0 with Ed25519 authentication.

Real-Time Event Types

EventSourceHandler
conductor.run.*Run lifecycle (created, updated, completed)conductorSlice
conductor.step.*Step execution progressconductorSlice
conductor.approval.*Approval gate triggeredapprovalSlice
conductor.evidence.*Evidence ledger entryconductorSlice
conductor.agent.statusAgent heartbeat / status changeagentSlice
conductor.server.statusMCP server connect/disconnectconductorSlice
agent.heartbeatPeriodic agent health checkagentSlice
handoff.*Agent-to-agent task handoffhandoffSlice
shared-context.updateShared context synchronizationsharedContextSlice
audit.entryAudit log entryauditSlice
budget.updatedBudget change notificationbudgetSlice
trust.policy.updatedPolicy rule changetrustPolicySlice
trust.evaluationReal-time policy evaluation resulttrustPolicySlice
anomaly.detectedAnomaly detection alertanomalySlice
run-event.*Run stdout/event streamingrunEventSlice

Connection Resilience

  • Automatic reconnection with exponential backoff (800ms base)
  • Nonce-based challenge-response authentication
  • Device identity persistence (Ed25519 keypair in localStorage)
  • Status tracking: disconnected → connecting → connected

Feature Flags

The Console uses a centralized feature flag system (60+ flags) allowing individual features to be enabled/disabled without code changes:
Core: gatewayEnabled, gatewayChat, gatewayFirstDataConductor: conductor, conductorGoals, conductorApprovals, conductorPolicy, conductorServers, conductorEvidence, conductorStateMachine, conductorContextTools, conductorEvidenceChain, conductorPersonaCanvas: canvasEditor, canvasExecution, workflowTemplates, n8nIntegrationTasks: tasksKanban, taskRunLink, taskAutoAssign, taskActivityLog, taskWorker, taskCheckoutLocking, runTemplatesAgent Management: agentManager, agentHeartbeat, agentHierarchy, agentConfigRevisions, agentSoulConfig, agentHandoffs, sharedContextIntelligence: crossSessionLearning, confidenceScoring, progressiveTrust, failureAnalysis, anomalyDetectionObservability: traces, sessions, observabilityDashboard, metricsDashboard, costTracking, costPredictionFinance: web3Dashboard, web3Swap, tradingDashboardInfrastructure: approvalGates, policyEditor, memoryPanel, schedules, webhooks, dataExport, mcpMarketplace, globalSearch, notificationCenter, openclawSettings, dryRunMode, rollbackEngine, humanAiCollaboration, dashboardSummary

How Console Maps to Protocol

The Console is the visual layer on top of SINT Protocol. Every Console action maps to a protocol operation:
Console ActionProtocol EndpointPackage
Create runPOST /v1/intercept@sint/gate-policy-gateway
Approve actionPOST /v1/approvals/:id/approveGateway server
Create policyPOST /conductor/policies@sint/gate-policy-gateway
View evidenceGET /v1/ledger@sint/gate-evidence-ledger
Generate proofPOST /v1/ledger/proof@sint/gate-evidence-ledger
Register agentPOST /v1/a2a/agents@sint/bridge-a2a
Check budgetGET /v1/economy/balance/:id@sint/bridge-economy
Canvas executeMultiple intercepts (batch)@sint/gate-policy-gateway
MCP tool callPOST /v1/intercept (MCP bridge)@sint/bridge-mcp
The Console works without the Protocol gateway — it falls back to REST API and then mock data for offline development. But full governance features require the gateway connection.

Tech Stack

LayerTechnology
FrameworkReact 19
StateRedux Toolkit 2.5 (31 slices)
RoutingReact Router 7 (32 routes)
Flow Editor@xyflow/react (React Flow)
ChartsRecharts + lightweight-charts
3DThree.js + @react-three/fiber
Web3wagmi, viem, ethers, @solana/web3.js, @cosmjs
AuthOIDC (react-oidc-context) + Ed25519 device identity
ValidationZod
Real-timeWebSocket JSON-RPC 2.0
TestingVitest — 110+ test files
BuildVite

Getting Started

git clone https://github.com/sint-ai/sint-agents.git
cd sint-agents
pnpm install
cp .env.example .env  # Configure VITE_BACKEND_URL, VITE_DASHBOARD_API_URL
pnpm dev
Connect to a running SINT Protocol gateway:
VITE_BACKEND_URL=http://localhost:4100
VITE_DASHBOARD_API_URL=http://localhost:3001

SINT Protocol

The governance engine the Console controls

Architecture

System architecture and package map