Plan your next pipeline
Explore your source catalog, choose the objects you need, and review a pipeline plan before creating it.
Supaflow for Snowflake CoCo
Tell Snowflake CoCo (formerly Cortex Code) what data you need. Explore your Supaflow connections, review a pipeline plan, and create it inside Snowsight. Ask for runs, job updates, and schedule changes in the same conversation.
You need a Supaflow account. Create an account or sign in.
Explore your source catalog, choose the objects you need, and review a pipeline plan before creating it.
Run an existing pipeline, follow its job status, and manage recurring schedules.
Inspect recent jobs and reported errors, then work out the next step with your assistant.
An administrator sets up the connector once. Each user connects their own Supaflow account and adds the skills that guide Snowflake CoCo.
A Snowflake administrator runs the setup SQL and grants connector access to the intended role. The guide includes the API integration, external MCP server, and role grants.
In the intended Supaflow account, open Settings → Admin → API Access. Enable API access and select Snowflake Cortex Code, the permission label for Snowflake CoCo, then save the access settings. An API key is not required.
Select the granted role in the Snowsight user menu. Open Settings → Personal agent settings → MCP connectors, choose Connect for Supaflow, and complete browser sign-in and consent.
Download the published Snowflake Labs repository. In the Snowflake CoCo Skills menu, upload the setup, using-supaflow, and setup-supaflow-native-app folders from plugins/supaflow/skills.
Supaflow maintains the OAuth client and callback. The guide uses one-day refresh validity, so users may need to reconnect daily. Skills uploaded this way are personal to you.
Your first conversation
Ask your assistant to verify your account, help you choose a workspace, and show the connections you can use. If something is missing, complete that setup in Supaflow and check again.
These are example prompts. The assistant should use your actual resources and report the results it finds.
The Supaflow Native App runs a private agent in your Snowflake account using Snowpark Container Services. Snowflake CoCo helps you manage the pipelines while the agent executes the work.
The Native App setup skill can guide installation and permissions using Snowflake SQL. Complete browser authorization, approve the Native App agent in the intended Supaflow account, and select your workspace before running pipelines.
Set up the Supaflow Native AppInstall the published Supaflow plugin from the Snowflake Labs repository. Use a Snowflake CoCo CLI version with HTTP MCP OAuth support, then connect your Supaflow account in the session.
Start Snowflake CoCo with your chosen Snowflake connection. Use /plugin list and /mcp to inspect Supaflow and connect. The CLI install is separate from Snowsight connector setup.
Yes. Snowflake CoCo is the new name for Cortex Code. Older recordings and the Supaflow permission label may still say Cortex Code. Use the Snowflake Cortex Code permission when connecting Snowflake CoCo.
A Snowflake administrator creates the external MCP connector once and grants access to your role. Enable API access and select the Snowflake Cortex Code permission in Supaflow, connect from Personal agent settings, then upload the three Supaflow skill folders from the Snowflake Labs repository. The setup guide includes the SQL and permissions.
No. Install the published plugin with the Snowflake CoCo CLI command for CLI sessions. Snowsight uses an account-level MCP connector and personally uploaded skills. Both connect to Supaflow through OAuth.
Pair Supaflow with the Native App to run its private agent in your Snowflake account using Snowpark Container Services. Install and authorize the app, approve the Native App agent in the intended Supaflow account, and select your workspace before running pipelines.
Supaflow maintains the production OAuth client and its callback. You authorize your own Supaflow account in the browser. Configure datasource credentials securely in Supaflow; never paste passwords, keys, or tokens into a conversation.
The documented Snowsight configuration uses a one-day refresh-token validity, so users may need to reconnect daily. Reconnect with the intended Supaflow account if the workspace is unexpected.