langstage-cli 0.6.26__tar.gz → 0.6.28__tar.gz

{langstage_cli-0.6.26/langstage_cli.egg-info → langstage_cli-0.6.28}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: langstage-cli
-Version: 0.6.26
+Version: 0.6.28
 Summary: The terminal stage for your LangGraph agent — Claude Code-style CLI for any CompiledGraph
 Author-email: Kedar Dabhadkar <kdabhadk@gmail.com>
 License-Expression: MIT
@@ -22,6 +22,7 @@ Requires-Dist: langgraph>=0.2.0
 Requires-Dist: langstage-core[agui]>=1.0.28
 Requires-Dist: click>=8.0.0
 Requires-Dist: python-dotenv
+Requires-Dist: langgraph-checkpoint-sqlite>=2.0.0
 Provides-Extra: dev
 Requires-Dist: pytest>=7.0.0; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"
@@ -101,6 +102,9 @@ This launches an interactive conversation loop with your agent.
 # Keyless demo agent — no API key, no agent of your own
 langstage-cli --demo "Hello"
 
+# Scaffold a runnable starter agent + langstage.toml (then just run it)
+langstage-cli init
+
 # Send a message directly to your agent
 langstage-cli -a my_agent.py:graph "Hello, agent!"
 
@@ -125,8 +129,47 @@ langstage-cli --demo
 # Print the resolved configuration: each value, its source, and the
 # env var / langstage.toml key that sets it
 langstage-cli --show-config
+
+# Resume a previous conversation across separate invocations
+langstage-cli "remember: my name is Kedar"   # a fresh, PERSISTED session
+langstage-cli -c "what's my name?"            # continue the most recent session
+langstage-cli --list-sessions                 # list resumable sessions
+langstage-cli --resume <id>                   # resume a specific one
+```
+
+## Getting started with your own agent
+
+```bash
+langstage-cli --demo "hi"     # see the CLI work, keyless
+langstage-cli init            # scaffold my_agent.py + langstage.toml (your own graph)
+langstage-cli "hi"            # runs MY agent — no -a, no hand-editing
 ```
 
+`init` writes a minimal, immediately-runnable starter agent (the stdlib `StateGraph`
+example below — needs only `langgraph`, a base dependency) plus a `langstage.toml`
+pointing at it, so the next `langstage-cli "..."` runs *your* graph. It refuses to
+overwrite an existing `my_agent.py` / `langstage.toml` unless you pass `--force`.
+
+## Resuming a session
+
+Every invocation persists its conversation to a durable, per-workspace store so a later
+run can pick it up — the terminal-agent continuity of Claude Code / Codex / Aider,
+without you baking a checkpointer into your own graph:
+
+- `--continue` / `-c` — resume the **most recent** session for this workspace and keep
+  going. If there's no prior session, it just starts a fresh one.
+- `--resume <id>` — resume a **specific** session (ids come from `--list-sessions`; a
+  bare `--resume` also lists them). A short prefix works if it's unambiguous.
+- A plain run with no flag starts a **new** session that is still persisted, so it can be
+  continued later.
+
+State lives in `~/.langstage/sessions/<workspace-hash>.sqlite` (honoring
+`LANGSTAGE_CONFIG_HOME`; override the whole location with `LANGSTAGE_CLI_SESSIONS_DIR`).
+Persistence is on by default — disable it with `--no-persist`, `LANGSTAGE_PERSIST=0`, or
+`[session] persist = false` in `langstage.toml`. A graph that compiles in its **own**
+checkpointer keeps it (yours always wins); the CLI only supplies a durable one when your
+graph has none. A pinned `[configurable] thread_id` now genuinely persists across runs.
+
 ## Commands
 
 In the interactive loop:
@@ -202,7 +245,15 @@ Options:
   --show-config                   Print the resolved configuration and exit
   -q, --quiet                     Scriptable single-shot output: only the reply
   --verify                        Preflight the agent (one real turn); exit 0/1
+  -c, --continue                  Resume the most recent session for this workspace
+  --resume [ID]                   Resume a specific session (bare: list them)
+  --list-sessions                 List resumable sessions for this workspace
+  --persist/--no-persist          Persist this session so it can be continued (default: on)
+  --force                         For `init`: overwrite existing files
   --version                       Show the version and exit
+
+Subcommand:
+  init                            Scaffold my_agent.py + langstage.toml in the current dir
 ```
 
 ### Verifying an agent (CI gate)

{langstage_cli-0.6.26 → langstage_cli-0.6.28}/README.md

@@ -64,6 +64,9 @@ This launches an interactive conversation loop with your agent.
 # Keyless demo agent — no API key, no agent of your own
 langstage-cli --demo "Hello"
 
+# Scaffold a runnable starter agent + langstage.toml (then just run it)
+langstage-cli init
+
 # Send a message directly to your agent
 langstage-cli -a my_agent.py:graph "Hello, agent!"
 
@@ -88,8 +91,47 @@ langstage-cli --demo
 # Print the resolved configuration: each value, its source, and the
 # env var / langstage.toml key that sets it
 langstage-cli --show-config
+
+# Resume a previous conversation across separate invocations
+langstage-cli "remember: my name is Kedar"   # a fresh, PERSISTED session
+langstage-cli -c "what's my name?"            # continue the most recent session
+langstage-cli --list-sessions                 # list resumable sessions
+langstage-cli --resume <id>                   # resume a specific one
+```
+
+## Getting started with your own agent
+
+```bash
+langstage-cli --demo "hi"     # see the CLI work, keyless
+langstage-cli init            # scaffold my_agent.py + langstage.toml (your own graph)
+langstage-cli "hi"            # runs MY agent — no -a, no hand-editing
 ```
 
+`init` writes a minimal, immediately-runnable starter agent (the stdlib `StateGraph`
+example below — needs only `langgraph`, a base dependency) plus a `langstage.toml`
+pointing at it, so the next `langstage-cli "..."` runs *your* graph. It refuses to
+overwrite an existing `my_agent.py` / `langstage.toml` unless you pass `--force`.
+
+## Resuming a session
+
+Every invocation persists its conversation to a durable, per-workspace store so a later
+run can pick it up — the terminal-agent continuity of Claude Code / Codex / Aider,
+without you baking a checkpointer into your own graph:
+
+- `--continue` / `-c` — resume the **most recent** session for this workspace and keep
+  going. If there's no prior session, it just starts a fresh one.
+- `--resume <id>` — resume a **specific** session (ids come from `--list-sessions`; a
+  bare `--resume` also lists them). A short prefix works if it's unambiguous.
+- A plain run with no flag starts a **new** session that is still persisted, so it can be
+  continued later.
+
+State lives in `~/.langstage/sessions/<workspace-hash>.sqlite` (honoring
+`LANGSTAGE_CONFIG_HOME`; override the whole location with `LANGSTAGE_CLI_SESSIONS_DIR`).
+Persistence is on by default — disable it with `--no-persist`, `LANGSTAGE_PERSIST=0`, or
+`[session] persist = false` in `langstage.toml`. A graph that compiles in its **own**
+checkpointer keeps it (yours always wins); the CLI only supplies a durable one when your
+graph has none. A pinned `[configurable] thread_id` now genuinely persists across runs.
+
 ## Commands
 
 In the interactive loop:
@@ -165,7 +207,15 @@ Options:
   --show-config                   Print the resolved configuration and exit
   -q, --quiet                     Scriptable single-shot output: only the reply
   --verify                        Preflight the agent (one real turn); exit 0/1
+  -c, --continue                  Resume the most recent session for this workspace
+  --resume [ID]                   Resume a specific session (bare: list them)
+  --list-sessions                 List resumable sessions for this workspace
+  --persist/--no-persist          Persist this session so it can be continued (default: on)
+  --force                         For `init`: overwrite existing files
   --version                       Show the version and exit
+
+Subcommand:
+  init                            Scaffold my_agent.py + langstage.toml in the current dir
 ```
 
 ### Verifying an agent (CI gate)