CocoPlus: an agentic workflow layer for Snowflake Coco projects

What CocoPlus adds on top of Coco

CocoPlus describes itself as an Agentic Operating System for Snowflake Coco. The problem it targets is not query writing. It is the absence of process around agent-driven data work: who captured the requirement, which specialist touched the model, what was reviewed before a production write, and what the last session left behind. CocoPlus answers with a fixed lifecycle (spec, plan, build, test, review, ship) plus phase gates and checkpoint-validated delivery, and it decomposes work across named specialist personas such as $de for Data Engineer, $ae for Analytics Engineer, $ds for Data Scientist, $da for Data Analyst, $bi, $dpm, $dst and $cdo. The audience is data engineering teams already inside the Snowflake Coco environment. The README is explicit that CocoPlus is built using only Coco-native constructs: Skills, Agents, Hooks and AGENTS.md. That is a deliberate constraint. It means the plugin has no separate runtime to operate, but it also means every capability is bounded by what Coco exposes.

How the phase gates and feature-owned runtime fit together

The architecture is layered. CocoFlow handles orchestration: tiered planning, pre-dispatch complexity scoring, committed run-policy snapshots, stage model floors, explicit human gates, dependency-group dispatch, dotted branch topology and synthesis passes. CocoSession handles continuity across long work with a PROGRESS handoff, predicate context, iteration and cost budgets with reserve landing, an operator kill-switch and canonical terminal statuses. Beneath both sits what the README calls a feature-owned runtime: hooks enqueue deterministic work through idempotent, feature-owned skill contracts, and CocoConsole is the only registered local runtime script. That last detail matters more than it looks. If hooks are the only path by which background work is scheduled, and each unit of work is idempotent, then a replayed queue should not duplicate meter, trace or flow artifacts. Version 2.0.2 states that queued hook follow-up work uses durable request envelopes, stable idempotency keys and skill-owned settlements for exactly this reason. The safety layer is a runtime policy engine: PreToolUse policies apply an allow() / deny() / instruct() model to Snowflake operations, with built-in protections for production DROP TABLE, TRUNCATE, DELETE without WHERE and production ALTER TABLE. Custom allow overrides for those built-ins are disabled unless explicitly configured, which is the right default and also the thing to check first if a legitimate operation keeps getting blocked.

Installing CocoPlus from GitHub and running a first project

Installation goes through Coco's managed plugin installer, not npm. The README gives two equivalent forms, a shorthand repository path and the full URL, followed by an enable step. Both lines are shown as plain text in the README rather than a shell block, so treat the leading token as the Coco CLI command and paste them into your Coco session.

cortex plugin install Snowflake-Labs/cocoplus
cortex plugin enable cocoplus

If you are working from a local checkout instead, run the install from the repository root with the force flag, then enable.

cortex plugin install . --force
cortex plugin enable cocoplus

The README lists two requirements: the Snowflake Coco CLI (cortex) with plugin support, and Node.js for hooks, which it notes is Windows, Mac and Linux compatible. Once enabled, the getting-started sequence initializes the project and turns features on.

$pod init
$cocoplus on
$spec

The $pod init step initializes CocoPlus in your project, $cocoplus on activates all features, and $spec starts the requirements phase. The README also lists $cocoplus console to open the read-only dashboard, $pilot on for CocoPilot natural-language orchestration, and $session status to inspect multi-session handoff and operator controls. Expect CocoConsole to be read-only: it exposes Flow, Cost, Sessions, Forge intent translation, Fleet Comms visibility and a Safety panel Policy Decision Log, but it is a control plane for observation, not a place to change policy.

Where CocoPlus gets in the way

The strongest limitation is also the most obvious: CocoPlus is not a standalone tool. It requires the Snowflake Coco CLI with plugin support, so if your team does not use Coco, nothing here applies and the installation command will not run. Node.js is a second hard requirement because hooks are implemented in JavaScript. The lifecycle itself is a cost. Phase gates, evidence checks and retained proposals mean work that used to be a single prompt now moves through staged transitions, and the README notes that stage transitions are inbox-first. The governance hooks ship with an observe/enforce rollout, which suggests the intended path is to watch what the policy engine would have blocked before turning enforcement on. Anyone expecting a drop-in prompt library will find the opposite: an opinionated process with migration skills, because older CocoPods are not simply compatible. The README says older project state is preserved through explicit migration skills and that new work should use the feature-owned skills directly. If you have an existing CocoPlus project, upgrading means running a migration, and the README does not document rollback for it. That is a gap worth knowing before you migrate anything you cannot recreate.

CocoPlus compared with plain Coco prompts or Streamlit dashboards

The nearest alternative is using Coco directly with your own prompts and AGENTS.md conventions. That approach has no install step beyond Coco itself, no migration path and no policy engine, and it stays entirely under your control. The difference in approach is that CocoPlus moves process out of individual prompts and into hooks and skill contracts, which is what makes phase gates and idempotent replay possible, but it also means your conventions now live in a plugin you have to upgrade. A second, less obvious comparison is a Streamlit app or a scheduled Snowflake TASK. Those give you a dashboard or a schedule, not a lifecycle. CocoPlus does include CocoRoutine, an opt-in path for scheduling completed self-contained flows as Snowflake TASKs with $routine, but the flow has to be finished and self-contained first. CocoConsole is also not a replacement for a BI surface: it is a local, read-only browser control plane for the agent run itself, covering flow, cost, sessions and policy decisions.

Upgrading, licence and the migration cost

The repository is licensed MIT, which is permissive and places few obligations on how you use or redistribute the plugin; the LICENSE file at the repository root is the authoritative text, and anything beyond that is a question for your own legal review. Maintenance signals are visible in the repository: the project is not archived, and the last push was on 2026-09-03. The README describes a V2.0.2 release with durable request envelopes and manifest-first memory in CocoWisdom, which tells you the memory layout changed: do-not-use.md stays universal, positive topic files load only when routed by stage or requested with $wisdom get, and branch-scoped memory remains plain Markdown for air-gap compatible review. Upgrading an existing project is a two-step command sequence.

$migrate v2 --dry-run
$migrate v2

The README instructs running the dry run first and says it reports the exact project-state changes, tests, validation checks and cleanup actions before anything is written. Budget for that review. The upgrade cost is not the install; it is reading the dry-run output and deciding whether the reported cleanup actions are acceptable for your repository.

Editorial conclusion

Adopt CocoPlus if your team already runs Snowflake Coco and wants phase gates, personas and a policy layer around agent work; skip it if you are not on Coco, since installation goes through cortex plugin install. Before rolling it out, run $migrate v2 --dry-run on one existing project and read the reported changes, then check whether the runtime policy engine's allow/deny/instruct model lines up with how your team treats production DROP TABLE and DELETE without WHERE.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. Snowflake-Labs/cocoplus on GitHub