forgeqe-cli 2.2.7__tar.gz → 2.4.0__tar.gz

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/LICENSE

@@ -1,6 +1,6 @@
 ForgeQE Software Licence
 
-Copyright (c) 2026 Javed Khan. All rights reserved.
+Copyright (c) 2026 Capgemini. All rights reserved.
 
 ForgeQE, its documentation, prompts, skills, and accompanying files (together, "the Software") are proprietary and confidential. The Software is licensed, not sold.
 

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: forgeqe-cli
-Version: 2.2.7
+Version: 2.4.0
 Summary: pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)
 Author: CLI-Agents
 License: MIT
@@ -42,6 +42,8 @@ Everything else is downloaded on first use into `~/.forgeqe/tools` (`%USERPROFIL
 
 `forgeqe setup` does all of this up front; otherwise the first command that needs a piece fetches it. Upgrading is `forgeqe update`: it updates every `forgeqe` on PATH (bun, npm and pip installs) and waits while the registries catch up with a new release. A release that pins a newer Bun, agent runtime, uv or engine library downloads it on the next run and removes the old one. Deleting `~/.forgeqe` removes everything ForgeQE downloaded. Behind a proxy, set `HTTPS_PROXY`. The npm launcher's Bun download also needs `NODE_USE_ENV_PROXY=1` (Node 24+); on older Node, use the pip launcher or install Bun yourself.
 
+**Coming from WebPilot** (`@capagents/webpilot`, ForgeQE's name before the rename): remove it first with `npm uninstall -g @capagents/webpilot`. npm refuses to install ForgeQE while the old package owns the `webpilot` command (`EEXIST ... npm\webpilot`). Your settings, sign-ins, `WEBPILOT_*` variables and `webpilot.yaml` files keep working. The npm package installs only the `forgeqe` command; the pip launcher still installs `webpilot` too. Install with `-g`, not with `npm install @capagents/forgeqe` inside a folder: `npx forgeqe` runs that folder copy, and `forgeqe update` does not change it (it prints how to replace it).
+
 From this repo:
 
 ```bash
@@ -73,7 +75,7 @@ npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/
 
 and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
 `cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
-expires, so do it just before the first release.
+expires, so do it just before the first release. Keep the workflow's file name: the registries trust it by name, and a renamed file cannot publish until each is told.
 
 ## Privacy
 
@@ -145,6 +147,14 @@ ForgeQE's agent needs the agent runtime (downloaded automatically, see Install)
 
 `forgeqe run` exits 0 when the job is done, 1 when it failed, 2 when it was stopped, and 3 when the agent needs more information.
 
+**For programs.** `forgeqe chat --jsonl` gives a program that needs a live agent (a web UI, an IDE) what the shell has: one agent for the whole conversation, follow-ups, credentials remembered for the session, questions and **Your turn** waits, and stop. It reads one JSON object per line on stdin and writes the agent's and the tools' events, the same ones the shell draws, as JSON lines on stdout; nothing else is ever written there, and remembered secrets and keys are redacted. It takes the flags of `forgeqe run`, plus `--carry-over FILE` to continue an earlier conversation. The protocol is in [HOW_TO_USE.md](HOW_TO_USE.md#a-live-agent-for-programs-forgeqe-chat---jsonl).
+
+```text
+→ {"v":1,"seq":1,"type":"ready","protocol":1,"version":"2.3.11","cwd":"/work/app","writeTests":true,"profile":{"name":"copilot","provider":"github_copilot"},"t":"…"}
+← {"type":"message","id":"m1","text":"Run SHOP-12 on staging"}
+→ {"v":1,"seq":9,"type":"turn_done","id":"m1","outcome":"done","reply":"SHOP-12 passed on staging.","next":[],"usage":{"input":5200,"output":310},"t":"…"}
+```
+
 `forgeqe --help` lists every command, among them `forgeqe db`, `forgeqe data` and `forgeqe flows` (see [Databases, test data, and data flows](#databases-test-data-and-data-flows)) and `forgeqe generated`, which says how much of the code ForgeQE wrote and how much is still there (`--json` for a pipeline).
 
 ## Page memory

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/README.md

@@ -27,6 +27,8 @@ Everything else is downloaded on first use into `~/.forgeqe/tools` (`%USERPROFIL
 
 `forgeqe setup` does all of this up front; otherwise the first command that needs a piece fetches it. Upgrading is `forgeqe update`: it updates every `forgeqe` on PATH (bun, npm and pip installs) and waits while the registries catch up with a new release. A release that pins a newer Bun, agent runtime, uv or engine library downloads it on the next run and removes the old one. Deleting `~/.forgeqe` removes everything ForgeQE downloaded. Behind a proxy, set `HTTPS_PROXY`. The npm launcher's Bun download also needs `NODE_USE_ENV_PROXY=1` (Node 24+); on older Node, use the pip launcher or install Bun yourself.
 
+**Coming from WebPilot** (`@capagents/webpilot`, ForgeQE's name before the rename): remove it first with `npm uninstall -g @capagents/webpilot`. npm refuses to install ForgeQE while the old package owns the `webpilot` command (`EEXIST ... npm\webpilot`). Your settings, sign-ins, `WEBPILOT_*` variables and `webpilot.yaml` files keep working. The npm package installs only the `forgeqe` command; the pip launcher still installs `webpilot` too. Install with `-g`, not with `npm install @capagents/forgeqe` inside a folder: `npx forgeqe` runs that folder copy, and `forgeqe update` does not change it (it prints how to replace it).
+
 From this repo:
 
 ```bash
@@ -58,7 +60,7 @@ npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/
 
 and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
 `cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
-expires, so do it just before the first release.
+expires, so do it just before the first release. Keep the workflow's file name: the registries trust it by name, and a renamed file cannot publish until each is told.
 
 ## Privacy
 
@@ -130,6 +132,14 @@ ForgeQE's agent needs the agent runtime (downloaded automatically, see Install)
 
 `forgeqe run` exits 0 when the job is done, 1 when it failed, 2 when it was stopped, and 3 when the agent needs more information.
 
+**For programs.** `forgeqe chat --jsonl` gives a program that needs a live agent (a web UI, an IDE) what the shell has: one agent for the whole conversation, follow-ups, credentials remembered for the session, questions and **Your turn** waits, and stop. It reads one JSON object per line on stdin and writes the agent's and the tools' events, the same ones the shell draws, as JSON lines on stdout; nothing else is ever written there, and remembered secrets and keys are redacted. It takes the flags of `forgeqe run`, plus `--carry-over FILE` to continue an earlier conversation. The protocol is in [HOW_TO_USE.md](HOW_TO_USE.md#a-live-agent-for-programs-forgeqe-chat---jsonl).
+
+```text
+→ {"v":1,"seq":1,"type":"ready","protocol":1,"version":"2.3.11","cwd":"/work/app","writeTests":true,"profile":{"name":"copilot","provider":"github_copilot"},"t":"…"}
+← {"type":"message","id":"m1","text":"Run SHOP-12 on staging"}
+→ {"v":1,"seq":9,"type":"turn_done","id":"m1","outcome":"done","reply":"SHOP-12 passed on staging.","next":[],"usage":{"input":5200,"output":310},"t":"…"}
+```
+
 `forgeqe --help` lists every command, among them `forgeqe db`, `forgeqe data` and `forgeqe flows` (see [Databases, test data, and data flows](#databases-test-data-and-data-flows)) and `forgeqe generated`, which says how much of the code ForgeQE wrote and how much is still there (`--json` for a pipeline).
 
 ## Page memory

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/py/forgeqe_cli/__init__.py

@@ -4,4 +4,4 @@ The agent itself is the npm package ``@capagents/forgeqe`` (OpenTUI + Bun).
 This distribution only puts a ``forgeqe`` command on PATH.
 """
 
-__version__ = "2.2.7"
+__version__ = "2.4.0"

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/py/forgeqe_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: forgeqe-cli
-Version: 2.2.7
+Version: 2.4.0
 Summary: pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)
 Author: CLI-Agents
 License: MIT
@@ -42,6 +42,8 @@ Everything else is downloaded on first use into `~/.forgeqe/tools` (`%USERPROFIL
 
 `forgeqe setup` does all of this up front; otherwise the first command that needs a piece fetches it. Upgrading is `forgeqe update`: it updates every `forgeqe` on PATH (bun, npm and pip installs) and waits while the registries catch up with a new release. A release that pins a newer Bun, agent runtime, uv or engine library downloads it on the next run and removes the old one. Deleting `~/.forgeqe` removes everything ForgeQE downloaded. Behind a proxy, set `HTTPS_PROXY`. The npm launcher's Bun download also needs `NODE_USE_ENV_PROXY=1` (Node 24+); on older Node, use the pip launcher or install Bun yourself.
 
+**Coming from WebPilot** (`@capagents/webpilot`, ForgeQE's name before the rename): remove it first with `npm uninstall -g @capagents/webpilot`. npm refuses to install ForgeQE while the old package owns the `webpilot` command (`EEXIST ... npm\webpilot`). Your settings, sign-ins, `WEBPILOT_*` variables and `webpilot.yaml` files keep working. The npm package installs only the `forgeqe` command; the pip launcher still installs `webpilot` too. Install with `-g`, not with `npm install @capagents/forgeqe` inside a folder: `npx forgeqe` runs that folder copy, and `forgeqe update` does not change it (it prints how to replace it).
+
 From this repo:
 
 ```bash
@@ -73,7 +75,7 @@ npm trust github @capagents/forgeqe --file forgeqe-release.yml --repo javed0211/
 
 and on pypi.org, under `forgeqe-cli` → Publishing, add a GitHub trusted publisher: owner `javed0211`, repository
 `cli-agents`, workflow `forgeqe-release.yml`, no environment. A new npm trust that has not published within 2 days
-expires, so do it just before the first release.
+expires, so do it just before the first release. Keep the workflow's file name: the registries trust it by name, and a renamed file cannot publish until each is told.
 
 ## Privacy
 
@@ -145,6 +147,14 @@ ForgeQE's agent needs the agent runtime (downloaded automatically, see Install)
 
 `forgeqe run` exits 0 when the job is done, 1 when it failed, 2 when it was stopped, and 3 when the agent needs more information.
 
+**For programs.** `forgeqe chat --jsonl` gives a program that needs a live agent (a web UI, an IDE) what the shell has: one agent for the whole conversation, follow-ups, credentials remembered for the session, questions and **Your turn** waits, and stop. It reads one JSON object per line on stdin and writes the agent's and the tools' events, the same ones the shell draws, as JSON lines on stdout; nothing else is ever written there, and remembered secrets and keys are redacted. It takes the flags of `forgeqe run`, plus `--carry-over FILE` to continue an earlier conversation. The protocol is in [HOW_TO_USE.md](HOW_TO_USE.md#a-live-agent-for-programs-forgeqe-chat---jsonl).
+
+```text
+→ {"v":1,"seq":1,"type":"ready","protocol":1,"version":"2.3.11","cwd":"/work/app","writeTests":true,"profile":{"name":"copilot","provider":"github_copilot"},"t":"…"}
+← {"type":"message","id":"m1","text":"Run SHOP-12 on staging"}
+→ {"v":1,"seq":9,"type":"turn_done","id":"m1","outcome":"done","reply":"SHOP-12 passed on staging.","next":[],"usage":{"input":5200,"output":310},"t":"…"}
+```
+
 `forgeqe --help` lists every command, among them `forgeqe db`, `forgeqe data` and `forgeqe flows` (see [Databases, test data, and data flows](#databases-test-data-and-data-flows)) and `forgeqe generated`, which says how much of the code ForgeQE wrote and how much is still there (`--json` for a pipeline).
 
 ## Page memory

{forgeqe_cli-2.2.7 → forgeqe_cli-2.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "forgeqe-cli"
-version = "2.2.7"
+version = "2.4.0"
 description = "pip launcher for the ForgeQE browser agent (npm package: @capagents/forgeqe)"
 readme = "README.md"
 requires-python = ">=3.9"