Back to Grip OSDeveloper Reference
Architecture & Framework
Four tiers. 19 Swift modules. 100+ MCP tools.
Grip OS is organized into four dependency tiers — from the upstream OpenClaw gateway through infrastructure, framework, and application layers. The core framework, GriposSwift, provides 19 SPM modules for building AI agents in Swift 6.2 with strict concurrency.
Architecture
Four-tier dependency model
Each tier depends only on the tier above it. Applications never reach past their immediate dependencies.
UpstreamRead-only upstream dependencies
openclaw/openclaw
Gateway, multi-channel AI assistant
mattt/AnyLanguageModel
LLM provider abstraction (v0.6.0)
@modelcontextprotocol/sdk
MCP standard (^1.26.0)
InfrastructureFleet, security, and routing
gripos-fleet
Fleet monorepo (submodules + addons)
gripos-sentinel
Security policy enforcement
gripos-brace
Unified proxy routing (:9000)
FrameworkCore Swift framework and data layer
gripos-swift
19 Swift modules (AI agents + fleet integration)
gripos-control
Mission Control data layer + UI
gripos-kernel
Platform daemon (always-on shared services)
ApplicationsEnd-user macOS applications
gripos-station
macOS operator workstation (menu bar app)
gripos-mail
Native macOS AI email client
gripos.dev
Marketing site
GriposSwift
19 modules. One SPM package.
A production-grade Swift AI agent framework aligned with @mastra/core@1.9.0. Built on AnyLanguageModel for provider-agnostic LLM integration.
SPM Install
.package(url: "https://github.com/nelsojona/gripos-swift", from: "0.1.0")Phase 1: Core FrameworkFully Implemented
MastraCoreCentral registry, config, model provider, errors, loggingMastraStorageKey-value storage, filesystem lifecycle, per-file write lockingMastraToolsTool protocol, registry, ToolProvider, built-in task toolsMastraObservabilityDistributed tracing (protocol stubs)MastraVoiceTTS/STT provider protocols (stubs)MastraEvalsScorers, Datasets, Experiments, ExperimentRunnerMastraRAGDocument chunking, embedding, vector store, RAG pipelineMastraMemoryConversation memory (in-memory + storage-backed)MastraMCPMCP client + MCPConfigStore for persisted server configsMastraAgentAI agent with ReAct loop, tool selection, security policyMastraWorkflowWorkflow engine — sequential, parallel, branch, loop stepsPhase 2: GatewayProtocol Stubs
GriposGatewayKitGateway WebSocket client protocol, frame typesGriposNodeKitNode identity, capability gate, command registryPhase 3: MCP BridgeProtocol Stubs
GriposMCPKitGripos-specific MCP client, safety gateMastraGriposBridgeUnified tool adapter between MCP and MastraPhase 4: Fleet ManagementFully Implemented
GriposFleetKitFleet client protocol, host/exec result modelsGriposFleetMCPAdapterFleet operations as MCP toolsMastraFleetToolsPolicy-gated fleet tools for agentsMastraStarterAgentsPre-configured agents (GatewayOps, FleetOps, MemoryOps, EmailOps)Brace Proxy
Unified ingress at :9000
A single port that routes to all backend services and bridges stdio MCP servers to HTTP/SSE. 100+ MCP tools across 7 servers.
| Route | Target | Protocol |
|---|---|---|
/gripos | Gateway :18789 | WebSocket |
/fleet | Fleet Gateway :18800 | WebSocket |
/canvas/* | Canvas :18793 | HTTP |
/mcp/menubar | gripos-mcp (stdio) | MCP bridge |
/mcp/filesystem | filesystem server | MCP bridge |
/mcp/github | GitHub MCP | MCP bridge |
/mcp/playwright | Playwright MCP | MCP bridge |
/mcp/context7 | Context7 docs | MCP bridge |
/mcp/serena | Semantic coding | MCP bridge |
/mcp/sentry | Error tracking | MCP bridge |
7 MCP servers bridged — 117 total tools. Auth: Bearer token on all routes except /health.