cinna-cli 0.1.0__py3-none-any.whl

cinna_cli-0.1.0.dist-info/METADATA

@@ -0,0 +1,231 @@
+Metadata-Version: 2.4
+Name: cinna-cli
+Version: 0.1.0
+Summary: Local development CLI for Cinna Core agents
+Project-URL: Homepage, https://github.com/opencinna/cinna-cli
+Project-URL: Repository, https://github.com/opencinna/cinna-cli
+Project-URL: Issues, https://github.com/opencinna/cinna-cli/issues
+Author-email: evgeny-l <evgeny-l@opencinna.io>
+License: MIT
+License-File: LICENSE.md
+Keywords: agents,cinna,cli,developer-tools,mcp,mutagen
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1
+Requires-Dist: httpx>=0.27
+Requires-Dist: mcp>=1.0
+Requires-Dist: rich>=13.0
+Requires-Dist: textual>=0.50
+Requires-Dist: websockets>=12.0
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# cinna-cli
+
+Local development CLI for [Cinna Core](https://github.com/opencinna/cinna-core) agents.
+
+Work on agent scripts, prompts, and webapps locally with your own editor and AI tools. The CLI keeps your workspace continuously synced with the remote agent environment, streams commands to it, and wires up MCP integration — so the platform is the single source of truth for runtime and credentials.
+
+## How It Works
+
+Cinna Core agents run in managed cloud environments. `cinna-cli` does **not** run a local Docker container. Instead:
+
+1. **Continuous sync** — [Mutagen](https://mutagen.io) keeps `./workspace` bidirectionally synced with the remote agent env over a WebSocket tunnel to the platform.
+2. **Remote exec** — `cinna exec <cmd>` streams your command through the platform to the remote env, with live stdout/stderr and the remote process's exit code.
+3. **MCP integration** — the local MCP proxy gives Claude Code / opencode access to the agent's knowledge base.
+
+```
+Your Editor / Claude Code
+        │
+        ▼
+  workspace/              ← edit locally
+        │
+  cinna sync (Mutagen) ◄──► Remote Agent Environment   (no local container)
+        │
+  cinna exec <cmd>       ── streaming output
+```
+
+## Prerequisites
+
+- **Python 3.10+**
+- **[Mutagen](https://mutagen.io)** (version pinned by the platform — `cinna setup` checks and prompts to install)
+
+## Getting Started
+
+Setup is initiated from the Cinna Core platform UI. Click **"Local Development"** on your agent's page to get a bootstrap command:
+
+```bash
+curl -s https://your-platform.com/api/cli-setup/TOKEN | python3 -
+```
+
+This will:
+
+1. Install `cinna-cli` (via `uv`, `pipx`, or `pip`)
+2. Exchange the setup token for CLI credentials
+3. Verify / prompt-install the required Mutagen version
+4. Clone the workspace (one-shot tarball; Mutagen takes over afterwards)
+5. Generate `CLAUDE.md`, `BUILDING_AGENT.md`, `.mcp.json`, `opencode.json`, `.gitignore`, `mutagen.yml`
+6. Start the continuous sync session
+
+After setup:
+
+```bash
+cd hr-manager-agent/
+cinna dev                           # start a foreground dev session (live sync + TUI)
+claude                              # open Claude Code (MCP tools auto-configured)
+cinna sync status                   # see sync state from another terminal
+cinna exec python scripts/main.py   # run a command in the remote env
+cinna list                          # see every agent registered on this machine
+```
+
+## Commands
+
+### `cinna setup <token_or_url>`
+
+Initialize a local workspace. Accepts the setup token, the URL, or the full curl command from the platform UI.
+
+The agent directory name is normalized to lowercase with dashes ("HR Manager Agent" → `hr-manager-agent/`).
+
+### `cinna set-token <token_or_url>`
+
+Refresh the CLI token on the current workspace without re-cloning. Run this from inside an existing agent directory when the stored token has expired — `cinna set-token` re-exchanges the setup token via `POST /api/cli-setup/{token}` and swaps the result into `.cinna/config.json` and `~/.cinna/agents.json` in place. Workspace files, `mutagen.yml`, and generated context files are left untouched.
+
+Accepts the same input forms as `cinna setup` (curl command, URL, or bare token). When only a bare token is given, the platform URL is reused from the workspace's existing `.cinna/config.json` — so you can refresh each agent from inside its own directory even if different agents live on different platforms. The exchanged token must belong to the same agent as the workspace; mismatched agent IDs abort the refresh.
+
+```bash
+cd hr-manager-agent/
+cinna set-token yWo36tbkdAOzrALxOEKq31_OA2iMelEg
+```
+
+### `cinna dev`
+
+Start a foreground dev session — creates / resumes the Mutagen sync session for this workspace and attaches the terminal to a two-tab TUI (status + raw Mutagen details). Ctrl-C terminates the session; sync does not outlive the TUI. To observe sync from another terminal without affecting it, use `cinna sync status`.
+
+### `cinna sync status | conflicts`
+
+Read-only views onto the live sync session (started by `cinna dev`).
+
+- `status` — state, pending changes, conflict count.
+- `conflicts` — list any conflict copies Mutagen has written. Resolve by picking a winner in your editor and deleting the `.conflict.*` copy.
+
+### `cinna exec <command…>`
+
+Stream a command through the platform to the remote agent environment. Output streams back live; Ctrl+C aborts. Exit code matches the remote process.
+
+```bash
+cinna exec python scripts/main.py
+cinna exec pip install pandas
+cinna exec 'bash -c "ls -la"'
+```
+
+### `cinna status`
+
+One-shot summary of the agent + current sync state. Includes a backend probe (`GET /sync-runtime`) that reports whether the stored CLI token is still accepted — `valid token`, `expired token`, or `no connection`. Use `cinna set-token` to refresh an expired token.
+
+### `cinna list`
+
+List every agent registered on this machine (from `~/.cinna/agents.json`). Three columns:
+
+1. **Agent** — display name on top, full agent ID below.
+2. **Location** — workspace path on top, platform UI link below. Missing directories are flagged in red.
+3. **Sync** — Mutagen session state on top (`active` / `paused` / `connecting` / `error`), plus a per-agent backend probe (`valid token` / `expired token` / `no connection`) on the bottom. The probes run in parallel with a short timeout so the view stays snappy even with many registered agents.
+
+### `cinna disconnect`
+
+Stop sync, remove `.cinna/` config and generated files (`CLAUDE.md`, `BUILDING_AGENT.md`, `.mcp.json`, `opencode.json`, `mutagen.yml`). Workspace files are preserved.
+
+### `cinna disconnect-all`
+
+Scan the current directory for every cinna workspace (directories containing `.cinna/config.json`), stop each sync session, and delete the directories entirely. Prompts for confirmation and prints a summary of what was removed.
+
+### `cinna completion [SHELL] [--install]`
+
+Output or install shell completion for bash, zsh, or fish.
+
+## Workspace Structure
+
+After setup, the agent directory looks like:
+
+```
+my-agent/
+  .cinna/                 # CLI config (do not edit)
+    config.json
+  workspace/              # Continuously synced with the remote env
+    scripts/              # Bundle-owned: agent Python scripts
+    docs/                 # Bundle-owned: WORKFLOW/ENTRYPOINT/REFINER prompts
+    webapp/               # Bundle-owned: dashboard + data endpoints
+    knowledge/            # Bundle-owned: static integration docs
+    files/                # Bundle-owned: static publisher-shipped assets
+    app-data/             # Per-user persistent — NOT shipped in bundle revisions.
+                          # Backed by a platform AppDataVolume keyed by (user_id, bundle_id);
+                          # mounted on the platform at /app/workspace/app-data.
+                          # Survives apply-update and uninstall/reinstall.
+      storage/            #   long-lived runtime output (DBs, reports, derived data)
+      uploads/            #   all user-supplied file uploads at runtime
+                          #   (chat attachments, task attachments, MCP uploads)
+      cache/              #   disposable caches
+    credentials/          # Backend-managed; visible read-only on your side
+    workspace_requirements.txt
+    workspace_system_packages.txt
+  mutagen.yml             # Sync rules (customizable)
+  CLAUDE.md               # Local dev instructions for AI tools
+  BUILDING_AGENT.md       # Building mode prompt pulled from the platform
+  .mcp.json               # MCP config for Claude Code
+  opencode.json           # MCP config for opencode
+  .gitignore              # ignores workspace/credentials/ and workspace/app-data/
+```
+
+**Persistence tiers** mirror the platform's bundle/install model:
+
+- **Bundle-owned** folders (`scripts/`, `docs/`, `webapp/`, `knowledge/`, `files/`, `workspace_requirements.txt`, `workspace_system_packages.txt`) are part of what gets snapshotted when a new bundle revision is published. As the developer/publisher, your edits here become the next shipped revision.
+- **`app-data/`** is the per-user persistent runtime volume. On the platform it lives in an `AppDataVolume` keyed by `(user_id, bundle_id)` — one volume per user per bundle, bind-mounted into the agent container at `/app/workspace/app-data`. It is **not** part of bundle revisions: when you publish, only the bundle-owned folders are snapshotted, and every user who installs your bundle gets their own fresh app-data volume. On the platform side the volume survives `apply-update` (bundle folders are overwritten, app-data is never touched) and uninstall/reinstall (orphaned, not deleted; reattaches by `bundle_id`). What you see synced to your local `workspace/app-data/` is your *own* developer install's app-data — useful for inspecting runtime output your scripts produce. It's gitignored by default since it's per-user runtime state, not bundle content.
+
+  Where scripts should put what:
+  - **`storage/`** — long-lived runtime state (databases, JSON, CSVs, generated reports). Anything the agent must keep across sessions and bundle updates.
+  - **`uploads/`** — every user-supplied file at runtime lands here automatically: chat attachments, task attachments, MCP `get_file_upload_url` uploads. Read from this folder, don't write to it from scripts.
+  - **`cache/`** — disposable caches the scripts may rebuild on demand.
+- **`credentials/`** is managed by the backend and only readable on your side.
+
+## Working with AI Coding Tools
+
+Setup generates MCP server configs for **Claude Code** (`.mcp.json`) and **opencode** (`opencode.json`), giving your AI tool a `knowledge_query` tool that searches the agent's knowledge base.
+
+```bash
+cd my-agent/
+claude        # or: opencode
+```
+
+## Sync & Conflict Resolution
+
+`cinna sync` drives Mutagen in `two-way-safe` mode with VCS-aware ignores. When the same file changes on both sides, Mutagen writes `<file>.conflict.<side>.<timestamp>` instead of picking a winner — inspect them with `cinna sync conflicts`, resolve, and delete the conflict copy.
+
+Large binary files and build artifacts are ignored by default (see `mutagen.yml`). Add your own ignores there if needed.
+
+## Development
+
+```bash
+git clone https://github.com/opencinna/cinna-cli.git
+cd cinna-cli
+uv venv && uv pip install -e ".[dev]"
+uv run pytest -v
+uv run ruff check src/
+```
+
+## License
+
+MIT

cinna_cli-0.1.0.dist-info/RECORD

@@ -0,0 +1,23 @@
+cinna/__init__.py,sha256=bOmc91LU6gdXMnmMbBfHhwF-y3xEi-QuXdGL9S4YiII,88
+cinna/auth.py,sha256=HTzv-qI9Dq2KLmYumoxrBGXgCqNErEROV3YqxyIRn-o,1312
+cinna/bootstrap.py,sha256=CMWh8S0ixdDZ8BsNP5um7uuOkFrKVwf0CeUKJn2LmmU,10550
+cinna/client.py,sha256=3iUYCacCJqdvJMFvfZlzfdQ1qkevEQOnznAMkqoD7EA,6199
+cinna/config.py,sha256=rF-oMTAYAztIJZo4oBezS-C2dPofADPKm0cPlFBAJe8,6454
+cinna/console.py,sha256=m2AN2DW1KQcjd-AwHSYZZu5zu4JQI4SBqfUimAyQA24,966
+cinna/context.py,sha256=EQ6GoBenEneMXbwsAouXnSqeTrF7fW7G-nK0dV4wnDM,7756
+cinna/errors.py,sha256=U-wo5tbz0wwRoDjkR4Jw0H5gzQTbrHmejlVyOfs5_no,1896
+cinna/logging.py,sha256=SzilkiYqnBaqrQGz6QuoF-4Ix0s0V5sXv7k09Mrnc-Y,1224
+cinna/main.py,sha256=6NBv9SVSCmjV0SLeYe-dp0m-UlS4Rmt3DFeaFGCqxKk,24747
+cinna/mcp_proxy.py,sha256=tBxh6c-dM6Ma-shTvbF86BPwy3Tilz4-9Js2xN_8vJ8,5118
+cinna/mutagen_runtime.py,sha256=roBbS-kLFPz2KoJC-4JXfD6Swbpbfi4XjLHmDfSrxEM,5636
+cinna/sync.py,sha256=aCVhXFN-h9YCdFF13a6e0Uyk6upXBQr6OpjyUH7SjKk,4274
+cinna/sync_session.py,sha256=E8GHa6hxGebQEI92CgTw6aAYinOT4O2kn2sOZ1w8I1A,14130
+cinna/sync_ssh_shim.py,sha256=zkI43K8mBka5-xCkKnbTLU2p_EYGcpqXwuDXMrE2DpE,7978
+cinna/sync_tui.py,sha256=SWzh9JvSw0Cd0E92Zu8Kr022vBa2D3Dm4Po8r3WeErQ,13816
+cinna/templates/CLAUDE.md.template,sha256=cTVQ2Dmaj8Lam7Ph2_wSl37G3bwlrvDk-_PLwOj38Pk,37272
+cinna/templates/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+cinna_cli-0.1.0.dist-info/METADATA,sha256=FEtWnVpR2ID757gm8fCZnxpUECMz1rfHcXUbkAisMr8,11844
+cinna_cli-0.1.0.dist-info/WHEEL,sha256=QccIxa26bgl1E6uMy58deGWi-0aeIkkangHcxk2kWfw,87
+cinna_cli-0.1.0.dist-info/entry_points.txt,sha256=DjNWWC4ZX1q4F3yjvrw4bI1svGeAG94la1ws1MjzL34,83
+cinna_cli-0.1.0.dist-info/licenses/LICENSE.md,sha256=gVEdPREa-NR6fUryFu-ZAyYB5qkipYPro6fIrndBbtc,1066
+cinna_cli-0.1.0.dist-info/RECORD,,

cinna_cli-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.29.0
+Root-Is-Purelib: true
+Tag: py3-none-any

cinna_cli-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+cinna = cinna.main:cli
+cinna-sync-ssh = cinna.sync_ssh_shim:main

cinna_cli-0.1.0.dist-info/licenses/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 OpenCinna
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.