Skip to content
Agents · Jul 15, 2026

Hugging Face details Shippy agent architecture and hosting platform

Allen Institute for AI's maritime agent uses Claude Opus 4.6, OpenClaw framework, and Mothership hosting platform with sandboxed sessions.

Trust79
HypeLow hype

1 source · cross-referenced

ShareXLinkedInEmail
TL;DR
  • Shippy is a maritime AI agent built by Allen Institute for AI (AI2) for high-stakes ocean monitoring decisions
  • Uses Claude Opus 4.6 as its LLM and OpenClaw agent framework
  • Skills are versioned markdown files; system prompt defines behavioral boundaries
  • Relies on Skylight API and a deterministic CLI wrapper to avoid nondeterministic API calls
  • Runs in ephemeral, user-isolated sessions via Mothership hosting platform

Allen Institute for AI (AI2) described the architecture and engineering lessons behind Shippy, a maritime AI agent built for high-stakes operational decisions where incorrect outputs carry real-world consequences.

Shippy’s design centers on reliability rather than model capability alone, with a focus on verifiable correctness against live data streams and continuous satellite and vessel signals rather than static snapshots.

The team decomposed the agent into three components: a soul (system prompt defining persona and behavioral boundaries), skills (versioned markdown files specifying how to handle requests), and config (runtime settings including the agent harness and model choice). Skills follow the same agent-skills specification used by coding agents like Claude Code and Codex.

Shippy currently relies on Claude Opus 4.6 as its LLM and uses OpenClaw, an open-source agent framework, as its runtime harness. The model and framework are configured at runtime via config changes rather than rebuilds, enabling swaps without altering the core agent artifact.

To constrain nondeterminism, Shippy interacts with the Skylight API through a purpose-built CLI that wraps complex API inputs—filter objects, pagination cursors, and geometry—into predictable commands. The CLI self-documents with extensive help text and writes outputs to local JSON files to avoid shell buffer limits and downstream tool breakage.

Under the CLI sits a standardized API layer exposing multiple resource types (events, vessels, regions, imagery, tracks) through typed schemas and common operations like search and aggregate. This layering allows each component—API, CLI, and skills—to be tested independently.

For multi-tenant safety, every user session runs in an ephemeral, isolated Kubernetes deployment via Mothership, AI2’s agent hosting platform. User-specific Skylight JWTs are injected at provision time, ensuring API calls and conversation history remain scoped to the individual analyst and never cross user boundaries.

The system prompt explicitly forbids legal determinations and speculation beyond supported data, making boundaries auditable and revisable without fine-tuning. Shippy can chain multiple skills in a single turn, such as combining Skylight data queries with partner databases like ProtectedSeas for marine protected area boundaries and Global Fishing Watch for vessel metadata.

Sources
  1. 01Hugging FaceWhat building Shippy taught us about building agents
Also on Agents

Stories may contain errors. Dispatch is assembled with AI assistance and curated by human editors; despite the trust-score filter, mistakes happen. We correct publicly — every article links to its revision history. Nothing here is financial, legal, or medical advice. Verify before relying on any claim.

© 2026 Dispatch. No ads. No sponsorships. No paid placement. Reader-supported via Ko-fi.

Built by a person who cares about honest AI news.