Your agents. Your environment.

Cortex Code,inside Glueprint.

Snowflake's Cortex Code coding agent. Glueprint runs Cortex Code over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.

Your provider account. Your code. A workspace to bring them together.

AG-401The integration01 / 05

Your chosen agent.A shared workspace.

Cortex Code is an AI agent built by Snowflake and integrated into the Snowflake platform for data engineering, analytics, machine learning, and agent-building tasks. Its agent framework interacts directly with a Snowflake environment, with awareness of Role-Based Access Control, schemas, and platform best practices. It ships in three forms - the Snowsight web UI, a desktop IDE for macOS and Windows, and a CLI - and supports MCP plus AGENTS.md customization.

Snowflake's Cortex Code coding agent.

Cortex Code connects over the open Agent Client Protocol. One generic adapter implements the protocol's client side, so Cortex Code gets the same surfaces as every other harness.

Everything below works with the Cortex Code CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.

Note

Best for

Snowflake users automating data engineering, analytics, and ML work inside their warehouse.

AG-402Install & connect02 / 05

Make it part ofyour next project.

Set up the integration on each machine where the agent will run.

  1. 01

    Open the ACP catalog

    On each execution host, open Settings -> Agents -> Browse ACP catalog and choose Cortex Code.

  2. 02

    Install and initialize

    Glueprint installs the registry distribution for Cortex Code, starts it, and completes the ACP initialize handshake.

  3. 03

    Start a project session

    Choose Cortex Code from a project or worktree and use the capabilities reported by that installed build.

The process stays on its host. Remote access follows your Glueprint plan and the capabilities of the installed agent.

Help with agent setup
AG-403How it works03 / 05

A direct connection.A shared view of the work.

Glueprint adds the workspace around the agent. Its provider account and configuration stay with the CLI.

  1. 01

    Glueprint spawns Cortex Code, not a fork

    Glueprint finds the Cortex Code binary you installed and spawns it, then speaks the Agent Client Protocol — JSON-RPC 2.0 over stdio — to drive it. Same CLI, same authentication; Glueprint just wraps the session.

  2. 02

    Output streams as structure

    Message chunks, tool calls, and tool-call updates from Cortex Code arrive as protocol notifications and render as the same live, typed timeline every Glueprint session gets — watchable from desktop, browser, or phone.

  3. 03

    Permission requests become approval cards

    When Cortex Code asks to write a file or run a command, the protocol's permission request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow per tool.

  4. 04

    One adapter, the whole fleet

    Because Cortex Code speaks ACP, adding it is a catalog entry, not an engineering project — the same adapter runs every other agent in the registry, so you can tile them side by side.

AG-404Compatibility04 / 05

Know what’savailable.

Some features come from Glueprint. Others depend on what the installed agent supports or reports when it connects.

Cortex Code capabilities and integration behavior
CapabilityStatusBehavior
Built by Snowflake, RBAC and schema awareRuntimeConfirmed when the installed agent connects.
Snowsight web, desktop IDE, and CLI modesRuntimeConfirmed when the installed agent connects.
Generates SQL and Python notebook codeRuntimeConfirmed when the installed agent connects.
MCP support for external tool connectionsRuntimeConfirmed when the installed agent connects.
Customizable via AGENTS.md and skillsRuntimeConfirmed when the installed agent connects.

Check the connected agent for its available models, modes, and permissions. Learn about ACP

AG-405Ownership & limits05 / 05

Your tools.Clear boundaries.

Credentials and model access follow the provider. Glueprint brings the surrounding work into one place.

Glueprint surface

Live sessions on every surface

Watch every Cortex Code prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.

Glueprint surface

Approve from your phone

Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.

Glueprint surface

Parallel sessions across worktrees

Run several Cortex Code sessions side by side, each in its own git worktree, with diffs, history, and a three-pane conflict resolver alongside.

Glueprint surface

Mix harnesses in one mosaic

Tile Cortex Code next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.

Glueprint surface

Persistent assistants

Promote it to an assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake.

Glueprint surface

Routines on a schedule

Wake it on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.

Glueprint surface

Analytics per harness

Messages, sessions, and output tokens computed from session logs — compare Cortex Code against Claude Code, Codex, and your other ACP agents.

Glueprint surface

Encrypted to the relay

Remote viewing rides AES-256-GCM envelope encryption. The relay routes; it cannot read.

AG-406A few useful answersNotes

Before youstart building.

Q.01Can I run Cortex Code with Glueprint?

Yes. Cortex Code is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Cortex Code CLI you already installed and drives it over JSON-RPC 2.0 — adding live sessions, inline approvals, worktrees, and remote control.

Q.02Do I need a separate Cortex Code subscription or API key?

No. Glueprint doesn't resell model access. Cortex Code authenticates exactly the way its vendor designed — its own login, subscription, or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.

Q.03Can I run Cortex Code from my phone?

Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams Cortex Code sessions live, lets you send follow-ups, and handles permission approvals from anywhere.

Q.04Can I run Cortex Code next to Claude Code and Codex?

Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics.

Q.05Is my session content private?

Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.

AG-407Go to the sourceOfficial resources

Officialresources.

Cortex Code · Registry version 1.0.73; proprietary; capabilities are validated on the execution host.

Agent information is sourced from Cortex Code's repository.

AG-409 The local tier is free

Your next project.A place to begin.

Download once, run on your hardware, scale up to teams when you're ready. No credit card.