Skip to main content

streamlit-coco

Bring Snowflake CoCo into Streamlit — streaming agent UI, tool cards you can actually read, and approval gates that fit governed data apps.

CI License

You own the page. CoCo owns the session. panel() streams the transcript; your app keeps st.chat_input, metrics, and forms. Approvals pause Write / Edit / Bash / SQL until someone clicks Approve once, Always allow, or Deny.

CoCo for Streamlit — streaming transcript with a Glob tool card

Alpha 0.1.0 — API may still move. Star / watch the repo if you plan to ship on it.

Repo: github.com/lletourmy/streamlit-coco (temporary PyPI source) · Dev: streamlit-coco-dev
SDK docs: Cortex Code Agent SDK


Why this package

Without streamlit-coco With streamlit-coco
Wire CoCo yourself across Streamlit reruns Session + fragment polling that keeps streaming
Raw JSON tool dumps Meaningful cards (Glob, Grep, Read, Write, SQL, AskUser…)
Hope the agent behaves require_approval_for + HITL UI
Chat-only demos Structured callbacks into your own widgets

Also: headless query() for scripts and CI, plus a legacy all-in-one chat() if you want built-in input.


Install

uv add "streamlit-coco[sdk]"
# or: pip install "streamlit-coco[sdk]"

From a clone (editable + tests):

make install

Prerequisites

  1. Python 3.10+ · Streamlit ≥ 1.53
  2. CoCo CLI on PATH (cortex --version)
  3. Authenticated Snowflake connection (~/.snowflake/connections.toml or equivalent)
  4. cortex-code-agent-sdk (pulled in by the sdk / dev extras)

Full local setup: doc/deployment/local.md (CLI install, Snowflake connections.toml, running examples, troubleshooting).
API: doc/api.md.


Quickstart

Preferred pattern — you own the input; CoCo owns the session and output:

import streamlit as st
import streamlit_coco as st_coco

opts = st_coco.CocoOptions(
    connection="analytics",
    cwd=".",
    allowed_tools=["Read", "Glob", "Grep"],
    require_approval_for=["Edit", "Write", "Bash"],
)

env = st_coco.check_environment(connection=opts.connection)
if not st_coco.render_start_gate(opts, session_key="copilot", env=env):
    st.stop()

session = st_coco.get_or_create_session(opts, key="copilot")
st_coco.panel(session=session, warm_up=True, show_status=True, run_every=0.25)
st_coco.chat_input_bar(session, placeholder="Ask CoCo…")
  • allowed_tools — may auto-run (enforced in Python when approvals are configured)
  • require_approval_for — pause for Approve once · Always allow · Deny

Legacy all-in-one component (built-in input):

st_coco.chat(session=session, key="coco_chat", height=560)

Try the demos

make chat          # panel + chat input + tool cards + approvals
make approval      # legacy CCv2 chat
make structured    # custom structured-output panel
make headless      # asyncio query() pipeline
make backlog       # Product Backlog Desk (multipage business demo)

Exploratory prompts: examples/testdata/prompts.json.
Backlog desk: examples/backlog_desk/README.md.


Patterns you’ll use often

Structured output → your widgets

output = st.container()

def render(data: dict, result: st_coco.CocoChatResult) -> None:
    with output:
        st.dataframe(data.get("selected_features", []))

st_coco.panel(session=session, on_structured_output=render)

Headless (no Streamlit UI)

import asyncio
import streamlit_coco as coco

async def run():
    async for event in coco.query("Profile ANALYTICS.CUSTOMERS"):
        if event.type == "result":
            print(event.structured_output)

asyncio.run(run())

What’s inside

Capability Entry points
Native panel + approvals panel(), chat_input_bar(), render_approvals()
Tool cards & AskUser / plan UI see doc/features/tools-display/
Session & options CocoSession, CocoOptions, get_or_create_session
Headless events query()
Legacy CCv2 chat()

API reference: doc/api.md.
Feature guides + release checklists: doc/features/README.md.

streamlit_coco/   # library (ui, session, permissions, tool cards, …)
examples/         # chat, approval, structured, headless demos
doc/             # PRD, roadmap, feature specs & checklists
tests/

Development

make install   # uv sync --extra dev
make check     # ruff + pytest
make audit     # pip-audit
make format    # ruff format + fix
make build     # sdist + wheel
make sync-release  # copy tree → ../streamlit-coco (see doc/deployment/publish.md)
make help      # all targets

CI runs lint, tests, and pip-audit on every PR to main.
Releases: develop here (streamlit-coco-dev), sync + tag on lletourmy/streamlit-coco → PyPI (guide).

Docs: PRD · API · Roadmap · Deployment · Changelog · AGENTS.md


License

Apache-2.0

Release files for streamlit-coco 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for streamlit-coco 0.1.5
File Size Uploaded
streamlit_coco-0.1.5.tar.gz 632.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for streamlit-coco 0.1.5
File Interpreter ABI Platform
streamlit_coco-0.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 697.3 kB

Release files / streamlit_coco-0.1.5.tar.gz

Download URL streamlit_coco-0.1.5.tar.gz
Size 632.0 kB
Tags Source
SHA-256 checksum
How to use checksums
13c2f1f5b6a66e053363aa1f58976e1668af3b8b40774b51b2ed99802aeedc4f
BLAKE2b-256 checksum
How to use checksums
e139fac0c1732fc96925f3923a085728d00ec18b0f9ec94fd91b9ad5f93c76a2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 9, 2026.

Transparency log

Release files / streamlit_coco-0.1.5-py3-none-any.whl

Download URL streamlit_coco-0.1.5-py3-none-any.whl
Size 65.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9d2bdb3b562f51d3f2f4a899b42564c8df82663fa1529e7357a26904b777eed1
BLAKE2b-256 checksum
How to use checksums
db8413453c794bfcad435db0858994daa6353c4c3dd0075198a00efaffa7cc24
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 9, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

This release

0.1.5 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page