deepcell-cli 0.6.1__tar.gz

deepcell_cli-0.6.1/PKG-INFO

@@ -0,0 +1,264 @@
+Metadata-Version: 2.4
+Name: deepcell-cli
+Version: 0.6.1
+Summary: Build and revise .deepcell documents from a terminal — the reasoning, the calculations, the document and the deck, with the links between them
+Author-email: DeepCell <hello@deepcell.net>
+License-Expression: MIT
+Project-URL: Homepage, https://deepcell.net
+Project-URL: Documentation, https://deepcell.net/product/cli
+Keywords: deepcell,cli,financial-modeling,business-intelligence
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: click>=8.1
+Requires-Dist: httpx>=0.28
+Requires-Dist: rich>=13.0
+Requires-Dist: mcp<2,>=1.26
+Requires-Dist: pyjwt>=2.8
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0; extra == "dev"
+Requires-Dist: respx>=0.22; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: jsonschema>=4.20; extra == "dev"
+
+# DeepCell CLI
+
+Command-line interface for **DeepCell** — a versionable `.deepcell` document that records the reasoning, the calculations, the document and the deck **together with the links between them**, so when an assumption changes you can see which conclusions still hold. AI agents read and write the format natively; this CLI is the primary tool for doing so from a terminal, script, or agent harness.
+
+```bash
+# macOS / Linux
+curl -LsSf https://beta.deepcell.net/install.sh | sh
+```
+
+```powershell
+# Windows (PowerShell)
+irm https://beta.deepcell.net/install.ps1 | iex
+```
+
+```bash
+deepcell --help
+deepcell-mcp --help           # MCP server (also included)
+```
+
+The installer picks uv or pip — whichever the machine has, fetching uv first if
+it has neither — finds where the console script actually landed, and adds that
+directory to your shell profiles so `deepcell` still resolves in the next
+shell. It handles the two cases a bare `pip install` does not: a stock Debian or
+Ubuntu image, which ships no pip, no `ensurepip` and no `venv` module, and a
+PEP 668 interpreter that refuses to install into itself. Running it twice is
+safe, and it verifies before reporting success.
+
+Prefer to install by hand? `deepcell-cli` is on PyPI:
+
+```bash
+uv tool install deepcell-cli
+uv tool update-shell
+```
+
+or `pip install deepcell-cli`.
+
+`deepcell: command not found` after installing by hand means the console script
+landed in a directory that is off `PATH` — not that the install failed. Re-run
+the installer above, which fixes exactly that; or use `python3 -m deepcell_cli`
+(`python -m` on Windows), which is the same CLI with no `PATH` involved.
+
+## Designed for agents
+
+The CLI is built to be driven programmatically:
+
+- **Machine-readable output.** Every command accepts `-f json` (also `table`, `plain`; default `plain`). Structured data goes to **stdout**, status/error messages to **stderr**, and failures exit non-zero — pipes and `jq` work cleanly:
+
+  ```bash
+  deepcell query model.deepcell Revenue FY2025E projected -f json | jq .value
+  ```
+
+- **Headless auth.** `deepcell register` creates an account without a browser; `DEEPCELL_ACCESS_TOKEN` injects a token for CI; `DEEPCELL_CONFIG` points at an alternate config file for session-scoped isolation.
+- **Non-interactive flags.** Destructive commands accept `-y`; `--project SLUG` targets a project per-invocation without mutating global state.
+- **Built-in workflow guidance.** `deepcell guide` lists the topics by workflow stage — `orient/start`, `generate/calcs`, `revise/scenarios`, `verify/lint`, `present/decks`, and the rest. Read one with `deepcell guide <topic>`, find one with `deepcell guide --search <text>`, and add the older flat topics with `deepcell guide --all`. When unsure how to model something, consult a guide topic before improvising.
+
+## Quick start
+
+```bash
+# 1. Authenticate — browser flow, or headless:
+deepcell login
+# deepcell register            # terminal-only account creation (CI/agents)
+
+# 2. Create and activate a project
+deepcell project create "My Project"
+deepcell project use my-project
+
+# 3. Work with files
+deepcell ls                                               # list files
+deepcell describe model.deepcell                          # inspect schema
+deepcell query model.deepcell Revenue FY2025E projected   # query one value
+deepcell query model.deepcell --sheet income_statement    # render a sheet
+deepcell edit model.deepcell Revenue_Growth FY2025E 0.12  # edit an assumption
+deepcell to-excel model.deepcell -o report.xlsx           # export to Excel
+```
+
+## Value addressing
+
+Every value is addressed by up to **five** dimensions:
+
+| Dimension | Role | Examples | If omitted |
+|-----------|------|----------|------------|
+| Item | what | `Revenue`, `COGS`, `WACC` | required |
+| Context | time period | `FY2025E`, `Q1_2024` | all contexts |
+| Status | actual vs. projected | `actual`, `projected` | all statuses |
+| Scenario (`--scenario`) | what-if branch | `bull`, `downside` | default scenario |
+| Custom dimensions (`--custom-dimensions`) | any extra axis | `geography:na;segment:cloud` | base cell |
+
+```bash
+deepcell query model.deepcell Revenue FY2025E projected
+deepcell query model.deepcell Revenue FY2025E --scenario bull
+deepcell query model.deepcell Revenue FY2025E --custom-dimensions "geography:na"
+deepcell cell-meta model.deepcell Revenue FY2025E    # formula, dependencies, provenance
+```
+
+The custom-dimension grammar is `dim:member`, semicolon-separated. Omitting a flag targets the **base cell**, never an error.
+
+## Editing: pick the right tool
+
+| You want to change… | Use | Why |
+|---------------------|-----|-----|
+| A hardcoded input (assumption, historical) | `deepcell edit FILE ITEM CTX VALUE` | literal Values |
+| A formula, item, period, scenario, sheet, format | `deepcell defs <op>` | structural, validated, atomic |
+| A computed cell → hardcoded override | `deepcell edit … --force` | flags the override explicitly |
+| A hardcoded cell → back to computed | `deepcell edit FILE ITEM CTX --clear` | lets the CalcDef re-govern it |
+| Raw XML (last resort) | `deepcell replace FILE OLD NEW` | string replacement with lint |
+
+Derived metrics belong in a **CalculationDefinition**, not hardcoded values — the engine recomputes every CalcDef on read (`deepcell guide generate/calcs`).
+
+```bash
+# Batch value edits (JSON array via file, inline, or stdin)
+deepcell edit model.deepcell --batch changes.json
+echo '[{"itemRef":"Revenue","contextRef":"FY2025E","newValue":"1500000","statusRef":"projected"}]' \
+  | deepcell edit model.deepcell --batch -
+
+# Structural edits
+deepcell defs add-item model.deepcell --name Gross_Profit --label "Gross Profit"
+deepcell defs add-calc model.deepcell --item Gross_Profit \
+  --formula "Revenue - COGS" --status projected --dry-run   # pre-flight, then re-run without --dry-run
+deepcell defs add-scenario model.deepcell --name Bull
+deepcell defs apply model.deepcell --ops ops.json     # many ops, atomically
+```
+
+`deepcell defs --help` lists the full op set: `add-* / update-* / delete-* / rename-* / reorder-*` for items, calcs, contexts/periods, scenarios, statuses, formats and rules, presentation blocks, and sensitivity tables, plus `header` for document metadata.
+
+## Command reference
+
+| Group | Commands |
+|-------|----------|
+| Auth | `login`, `register`, `logout`, `whoami`, `verify-email`, `account` |
+| Projects | `project list / use / create / info` |
+| Files | `ls`, `cat`, `write`, `rm`, `download` |
+| Inspection | `describe`, `query`, `cell-meta`, `relationships`, `grep`, `doctor` |
+| Editing | `edit`, `defs`, `replace`, `variant checkout / create / diff / merge / list` |
+| Document surface | `doc` — outline, blocks, body, links, lint |
+| Deck surface | `deck` — slides, ordering, binding, branding |
+| Change review | `changes list / diff / revert`, `impact` |
+| Version control | `log`, `diff`, `restore` |
+| Sync | `clone`, `status`, `pull`, `push`, `commit`, `merge` |
+| Import / export | `import`, `ingest`, `to-excel`, `to-docx`, `to-pptx`, `to-pdf` |
+| Reasoning | `reasoning`, `reasoning-diff`, `claim`, `assumption` |
+| Delivery | `viewer`, `share create / list / revoke` |
+| Knowledge | `help`, `guide`, `rules`, `ref`, `example` |
+
+Run `deepcell <command> --help` for detailed usage — the help text includes worked examples for every mode.
+
+## Reasoning
+
+`.deepcell` files carry a typed reasoning graph — **Claims**, **Assumptions**, **Evidence**, connected by **Argument** edges — so a model explains *why* its numbers are what they are:
+
+```bash
+deepcell reasoning add-claim model.deepcell --id rev-thesis --kind thesis \
+  --label "Revenue doubles by FY27" --item-refs Revenue
+deepcell reasoning graph model.deepcell        # render as Mermaid
+deepcell reasoning impact model.deepcell rev-thesis   # what depends on this claim?
+deepcell reasoning lint model.deepcell         # structural checks
+deepcell claim model.deepcell                  # inspect claims
+deepcell assumption model.deepcell             # inspect assumptions
+```
+
+See `deepcell guide revise/reasoning` and `deepcell guide verify/review`.
+
+## Variants, history, and merge
+
+```bash
+deepcell variant create "Best Case"       # parallel assumption set, no file copies
+deepcell variant checkout best-case
+deepcell variant diff best-case           # vs main
+deepcell variant merge best-case
+
+deepcell log                              # like git log
+deepcell diff abc123 def456               # compare two revisions
+deepcell restore abc123                   # like git checkout
+
+deepcell merge resolve model.deepcell     # semantic 3-way merge of sync conflicts
+deepcell merge resolve model.deepcell --ours   # keep local values (--theirs: remote)
+```
+
+## Sync (local ↔ cloud)
+
+```bash
+deepcell clone my-project              # download to ./my-project/
+cd my-project
+# ... edit files locally ...
+deepcell status                          # A/M/D vs last sync
+deepcell push -m "Updated assumptions"   # upload
+deepcell pull                            # fetch cloud changes
+```
+
+A `.deepcell/` metadata directory tracks the project link and sync state. `push` refuses to clobber cloud changes — it asks you to `pull` first. See `deepcell guide revise/history`.
+
+## Import & export
+
+```bash
+deepcell import revenue.xlsx --items items.json --contexts contexts.json \
+  --aggregations aggregations.json --keep-raw
+deepcell to-excel model.deepcell -o report.xlsx --formulas   # live Excel formulas
+deepcell to-docx model.deepcell -o memo.docx                 # the document, as Word
+deepcell to-pptx model.deepcell -o deck.pptx                 # HTML deck → editable PowerPoint
+deepcell to-pdf model.deepcell -o memo.pdf                   # the document, as PDF
+deepcell ingest cn ...                                        # A-share (cninfo) filings
+```
+
+`--aggregations` maps and combines source rows into target coordinates (`SUM`, `AVERAGE`, `MIN`, `MAX`, `COUNT`); `--keep-raw` retains originals alongside. See `deepcell guide excel-import` and `deepcell guide schema-matching`.
+
+## MCP server
+
+The package ships `deepcell-mcp`, exposing the whole CLI to MCP clients (Claude Code, Claude.ai, and others) as a single `deepcell(command)` tool:
+
+```bash
+deepcell-mcp                      # stdio transport (local)
+deepcell-mcp --http               # streamable-http on 127.0.0.1:8080
+```
+
+Interactive and sync commands (`login`, `clone`, `push`, …) are blocked inside MCP; authenticate with an API key or OAuth instead.
+
+## Environment variables
+
+| Variable | Purpose | Default |
+|----------|---------|---------|
+| `DEEPCELL_API_URL` | API endpoint | `https://beta.deepcell.net/api/jingwei` |
+| `DEEPCELL_PROJECT` | Override active project | _(none)_ |
+| `DEEPCELL_ACCESS_TOKEN` | Auth token for CI/headless use | _(none)_ |
+| `DEEPCELL_CONFIG` | Alternate `config.json` path (session-scoped) | `~/.deepcell/config.json` |
+| `DEEPCELL_NO_ANON` | Opt out of the anonymous first-use session | _(unset)_ |
+| `DEEPCELL_NO_UPGRADE_CHECK` | Silence the upgrade-available notice for this process | _(unset)_ |
+
+Precedence: per-invocation flags (`--project`) > environment > `~/.deepcell/config.json`. Credentials live in `~/.deepcell/credentials.json` (`0600`); token refresh is automatic.
+
+## License
+
+MIT. The CLI is developed in a private repository, so there is no public source
+link to follow from here — the licence is what ships in the package metadata.

deepcell_cli-0.6.1/README.md

@@ -0,0 +1,232 @@
+# DeepCell CLI
+
+Command-line interface for **DeepCell** — a versionable `.deepcell` document that records the reasoning, the calculations, the document and the deck **together with the links between them**, so when an assumption changes you can see which conclusions still hold. AI agents read and write the format natively; this CLI is the primary tool for doing so from a terminal, script, or agent harness.
+
+```bash
+# macOS / Linux
+curl -LsSf https://beta.deepcell.net/install.sh | sh
+```
+
+```powershell
+# Windows (PowerShell)
+irm https://beta.deepcell.net/install.ps1 | iex
+```
+
+```bash
+deepcell --help
+deepcell-mcp --help           # MCP server (also included)
+```
+
+The installer picks uv or pip — whichever the machine has, fetching uv first if
+it has neither — finds where the console script actually landed, and adds that
+directory to your shell profiles so `deepcell` still resolves in the next
+shell. It handles the two cases a bare `pip install` does not: a stock Debian or
+Ubuntu image, which ships no pip, no `ensurepip` and no `venv` module, and a
+PEP 668 interpreter that refuses to install into itself. Running it twice is
+safe, and it verifies before reporting success.
+
+Prefer to install by hand? `deepcell-cli` is on PyPI:
+
+```bash
+uv tool install deepcell-cli
+uv tool update-shell
+```
+
+or `pip install deepcell-cli`.
+
+`deepcell: command not found` after installing by hand means the console script
+landed in a directory that is off `PATH` — not that the install failed. Re-run
+the installer above, which fixes exactly that; or use `python3 -m deepcell_cli`
+(`python -m` on Windows), which is the same CLI with no `PATH` involved.
+
+## Designed for agents
+
+The CLI is built to be driven programmatically:
+
+- **Machine-readable output.** Every command accepts `-f json` (also `table`, `plain`; default `plain`). Structured data goes to **stdout**, status/error messages to **stderr**, and failures exit non-zero — pipes and `jq` work cleanly:
+
+  ```bash
+  deepcell query model.deepcell Revenue FY2025E projected -f json | jq .value
+  ```
+
+- **Headless auth.** `deepcell register` creates an account without a browser; `DEEPCELL_ACCESS_TOKEN` injects a token for CI; `DEEPCELL_CONFIG` points at an alternate config file for session-scoped isolation.
+- **Non-interactive flags.** Destructive commands accept `-y`; `--project SLUG` targets a project per-invocation without mutating global state.
+- **Built-in workflow guidance.** `deepcell guide` lists the topics by workflow stage — `orient/start`, `generate/calcs`, `revise/scenarios`, `verify/lint`, `present/decks`, and the rest. Read one with `deepcell guide <topic>`, find one with `deepcell guide --search <text>`, and add the older flat topics with `deepcell guide --all`. When unsure how to model something, consult a guide topic before improvising.
+
+## Quick start
+
+```bash
+# 1. Authenticate — browser flow, or headless:
+deepcell login
+# deepcell register            # terminal-only account creation (CI/agents)
+
+# 2. Create and activate a project
+deepcell project create "My Project"
+deepcell project use my-project
+
+# 3. Work with files
+deepcell ls                                               # list files
+deepcell describe model.deepcell                          # inspect schema
+deepcell query model.deepcell Revenue FY2025E projected   # query one value
+deepcell query model.deepcell --sheet income_statement    # render a sheet
+deepcell edit model.deepcell Revenue_Growth FY2025E 0.12  # edit an assumption
+deepcell to-excel model.deepcell -o report.xlsx           # export to Excel
+```
+
+## Value addressing
+
+Every value is addressed by up to **five** dimensions:
+
+| Dimension | Role | Examples | If omitted |
+|-----------|------|----------|------------|
+| Item | what | `Revenue`, `COGS`, `WACC` | required |
+| Context | time period | `FY2025E`, `Q1_2024` | all contexts |
+| Status | actual vs. projected | `actual`, `projected` | all statuses |
+| Scenario (`--scenario`) | what-if branch | `bull`, `downside` | default scenario |
+| Custom dimensions (`--custom-dimensions`) | any extra axis | `geography:na;segment:cloud` | base cell |
+
+```bash
+deepcell query model.deepcell Revenue FY2025E projected
+deepcell query model.deepcell Revenue FY2025E --scenario bull
+deepcell query model.deepcell Revenue FY2025E --custom-dimensions "geography:na"
+deepcell cell-meta model.deepcell Revenue FY2025E    # formula, dependencies, provenance
+```
+
+The custom-dimension grammar is `dim:member`, semicolon-separated. Omitting a flag targets the **base cell**, never an error.
+
+## Editing: pick the right tool
+
+| You want to change… | Use | Why |
+|---------------------|-----|-----|
+| A hardcoded input (assumption, historical) | `deepcell edit FILE ITEM CTX VALUE` | literal Values |
+| A formula, item, period, scenario, sheet, format | `deepcell defs <op>` | structural, validated, atomic |
+| A computed cell → hardcoded override | `deepcell edit … --force` | flags the override explicitly |
+| A hardcoded cell → back to computed | `deepcell edit FILE ITEM CTX --clear` | lets the CalcDef re-govern it |
+| Raw XML (last resort) | `deepcell replace FILE OLD NEW` | string replacement with lint |
+
+Derived metrics belong in a **CalculationDefinition**, not hardcoded values — the engine recomputes every CalcDef on read (`deepcell guide generate/calcs`).
+
+```bash
+# Batch value edits (JSON array via file, inline, or stdin)
+deepcell edit model.deepcell --batch changes.json
+echo '[{"itemRef":"Revenue","contextRef":"FY2025E","newValue":"1500000","statusRef":"projected"}]' \
+  | deepcell edit model.deepcell --batch -
+
+# Structural edits
+deepcell defs add-item model.deepcell --name Gross_Profit --label "Gross Profit"
+deepcell defs add-calc model.deepcell --item Gross_Profit \
+  --formula "Revenue - COGS" --status projected --dry-run   # pre-flight, then re-run without --dry-run
+deepcell defs add-scenario model.deepcell --name Bull
+deepcell defs apply model.deepcell --ops ops.json     # many ops, atomically
+```
+
+`deepcell defs --help` lists the full op set: `add-* / update-* / delete-* / rename-* / reorder-*` for items, calcs, contexts/periods, scenarios, statuses, formats and rules, presentation blocks, and sensitivity tables, plus `header` for document metadata.
+
+## Command reference
+
+| Group | Commands |
+|-------|----------|
+| Auth | `login`, `register`, `logout`, `whoami`, `verify-email`, `account` |
+| Projects | `project list / use / create / info` |
+| Files | `ls`, `cat`, `write`, `rm`, `download` |
+| Inspection | `describe`, `query`, `cell-meta`, `relationships`, `grep`, `doctor` |
+| Editing | `edit`, `defs`, `replace`, `variant checkout / create / diff / merge / list` |
+| Document surface | `doc` — outline, blocks, body, links, lint |
+| Deck surface | `deck` — slides, ordering, binding, branding |
+| Change review | `changes list / diff / revert`, `impact` |
+| Version control | `log`, `diff`, `restore` |
+| Sync | `clone`, `status`, `pull`, `push`, `commit`, `merge` |
+| Import / export | `import`, `ingest`, `to-excel`, `to-docx`, `to-pptx`, `to-pdf` |
+| Reasoning | `reasoning`, `reasoning-diff`, `claim`, `assumption` |
+| Delivery | `viewer`, `share create / list / revoke` |
+| Knowledge | `help`, `guide`, `rules`, `ref`, `example` |
+
+Run `deepcell <command> --help` for detailed usage — the help text includes worked examples for every mode.
+
+## Reasoning
+
+`.deepcell` files carry a typed reasoning graph — **Claims**, **Assumptions**, **Evidence**, connected by **Argument** edges — so a model explains *why* its numbers are what they are:
+
+```bash
+deepcell reasoning add-claim model.deepcell --id rev-thesis --kind thesis \
+  --label "Revenue doubles by FY27" --item-refs Revenue
+deepcell reasoning graph model.deepcell        # render as Mermaid
+deepcell reasoning impact model.deepcell rev-thesis   # what depends on this claim?
+deepcell reasoning lint model.deepcell         # structural checks
+deepcell claim model.deepcell                  # inspect claims
+deepcell assumption model.deepcell             # inspect assumptions
+```
+
+See `deepcell guide revise/reasoning` and `deepcell guide verify/review`.
+
+## Variants, history, and merge
+
+```bash
+deepcell variant create "Best Case"       # parallel assumption set, no file copies
+deepcell variant checkout best-case
+deepcell variant diff best-case           # vs main
+deepcell variant merge best-case
+
+deepcell log                              # like git log
+deepcell diff abc123 def456               # compare two revisions
+deepcell restore abc123                   # like git checkout
+
+deepcell merge resolve model.deepcell     # semantic 3-way merge of sync conflicts
+deepcell merge resolve model.deepcell --ours   # keep local values (--theirs: remote)
+```
+
+## Sync (local ↔ cloud)
+
+```bash
+deepcell clone my-project              # download to ./my-project/
+cd my-project
+# ... edit files locally ...
+deepcell status                          # A/M/D vs last sync
+deepcell push -m "Updated assumptions"   # upload
+deepcell pull                            # fetch cloud changes
+```
+
+A `.deepcell/` metadata directory tracks the project link and sync state. `push` refuses to clobber cloud changes — it asks you to `pull` first. See `deepcell guide revise/history`.
+
+## Import & export
+
+```bash
+deepcell import revenue.xlsx --items items.json --contexts contexts.json \
+  --aggregations aggregations.json --keep-raw
+deepcell to-excel model.deepcell -o report.xlsx --formulas   # live Excel formulas
+deepcell to-docx model.deepcell -o memo.docx                 # the document, as Word
+deepcell to-pptx model.deepcell -o deck.pptx                 # HTML deck → editable PowerPoint
+deepcell to-pdf model.deepcell -o memo.pdf                   # the document, as PDF
+deepcell ingest cn ...                                        # A-share (cninfo) filings
+```
+
+`--aggregations` maps and combines source rows into target coordinates (`SUM`, `AVERAGE`, `MIN`, `MAX`, `COUNT`); `--keep-raw` retains originals alongside. See `deepcell guide excel-import` and `deepcell guide schema-matching`.
+
+## MCP server
+
+The package ships `deepcell-mcp`, exposing the whole CLI to MCP clients (Claude Code, Claude.ai, and others) as a single `deepcell(command)` tool:
+
+```bash
+deepcell-mcp                      # stdio transport (local)
+deepcell-mcp --http               # streamable-http on 127.0.0.1:8080
+```
+
+Interactive and sync commands (`login`, `clone`, `push`, …) are blocked inside MCP; authenticate with an API key or OAuth instead.
+
+## Environment variables
+
+| Variable | Purpose | Default |
+|----------|---------|---------|
+| `DEEPCELL_API_URL` | API endpoint | `https://beta.deepcell.net/api/jingwei` |
+| `DEEPCELL_PROJECT` | Override active project | _(none)_ |
+| `DEEPCELL_ACCESS_TOKEN` | Auth token for CI/headless use | _(none)_ |
+| `DEEPCELL_CONFIG` | Alternate `config.json` path (session-scoped) | `~/.deepcell/config.json` |
+| `DEEPCELL_NO_ANON` | Opt out of the anonymous first-use session | _(unset)_ |
+| `DEEPCELL_NO_UPGRADE_CHECK` | Silence the upgrade-available notice for this process | _(unset)_ |
+
+Precedence: per-invocation flags (`--project`) > environment > `~/.deepcell/config.json`. Credentials live in `~/.deepcell/credentials.json` (`0600`); token refresh is automatic.
+
+## License
+
+MIT. The CLI is developed in a private repository, so there is no public source
+link to follow from here — the licence is what ships in the package metadata.

deepcell_cli-0.6.1/pyproject.toml

@@ -0,0 +1,75 @@
+[project]
+name = "deepcell-cli"
+version = "0.6.1"
+description = "Build and revise .deepcell documents from a terminal — the reasoning, the calculations, the document and the deck, with the links between them"
+readme = "README.md"
+license = "MIT"
+requires-python = ">=3.10"
+authors = [{ name = "DeepCell", email = "hello@deepcell.net" }]
+keywords = ["deepcell", "cli", "financial-modeling", "business-intelligence"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    # Two audiences on purpose. Finance is the deepest pack, but it is
+    # deliberately the minority of the example library (tests/test_packs.py
+    # fails if the core path stops carrying at least three non-finance
+    # examples), and the CLI's own pitch is that it is driven by agents.
+    "Intended Audience :: Developers",
+    "Intended Audience :: Financial and Insurance Industry",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Office/Business :: Financial",
+]
+# mcp is pinned below 2.0: the v2 SDK (released 2026-07-28, alongside the
+# 2026-07-28 spec) renamed FastMCP to MCPServer and moved it to
+# mcp.server.mcpserver, with no shim at the old path. An unbounded `mcp>=1.0`
+# resolved to 2.0.0 on the next image build and crash-looped deepcell-mcp on
+# `from mcp.server.fastmcp import FastMCP`. Lifting this ceiling means porting
+# mcp_server.py and oauth_provider.py to the v2 API — not a resolver's call.
+dependencies = ["click>=8.1", "httpx>=0.28", "rich>=13.0", "mcp>=1.26,<2", "pyjwt>=2.8"]
+
+[project.optional-dependencies]
+dev = ["pytest>=7.0", "respx>=0.22", "pytest-asyncio>=0.23", "jsonschema>=4.20"]
+
+[project.scripts]
+deepcell = "deepcell_cli.main:cli"
+deepcell-mcp = "deepcell_cli.mcp_server:main"
+
+# These become the sidebar links on the PyPI project page. There is
+# deliberately no Repository or Issues entry: the CLI is developed in a private
+# repository, and a link to one nobody can open is worse than no link.
+#
+# deepcell.net is the canonical host the site is moving to shortly; it does not
+# resolve yet, so these two links go live when the domain does. That is a
+# deliberate trade for not stamping the outgoing beta host into the metadata of
+# a release that cannot be re-uploaded. The installer URLs are NOT part of it —
+# they stay on beta.deepcell.net, because a curl that 404s is a broken install
+# today rather than a link that is briefly grey.
+[project.urls]
+Homepage = "https://deepcell.net"
+Documentation = "https://deepcell.net/product/cli"
+
+[build-system]
+requires = ["setuptools>=73.0.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+deepcell_cli = ["capability-contract.json"]
+
+[dependency-groups]
+dev = [
+    "openpyxl>=3.1.5",
+    "pytest>=9.0.2",
+    "pytest-asyncio>=0.23",
+    "respx>=0.22.0",
+]
+
+[tool.pytest.ini_options]
+asyncio_mode = "strict"
+testpaths = ["tests"]

deepcell_cli-0.6.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

deepcell_cli-0.6.1/src/deepcell_cli/__init__.py

@@ -0,0 +1,12 @@
+"""DeepCell CLI — command-line interface for the DeepCell platform.
+
+``__version__`` is the *runtime* version — what `--version` prints, what the
+client header sends, and what the upgrade check compares against PyPI. The
+packaging version in ``cli/pyproject.toml`` is a second copy that must say the
+same thing, and a third is stamped into ``docs/cli-surface.json`` by
+``scripts/gen_cli_surface.py``. All three are pinned together by
+``cli/tests/test_version_parity.py`` — bumping one alone ships a build that
+reports a version it is not, and skipping the regen lands a red build.
+"""
+
+__version__ = "0.6.1"

deepcell_cli-0.6.1/src/deepcell_cli/__main__.py

@@ -0,0 +1,5 @@
+"""Allow running as ``python -m deepcell_cli``."""
+
+from deepcell_cli.main import cli
+
+cli()