loopsmith-cli 0.2.0__tar.gz → 0.2.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/PKG-INFO +44 -5
  2. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/README.md +42 -3
  3. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/pyproject.toml +2 -2
  4. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli/__init__.py +1 -1
  5. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/PKG-INFO +44 -5
  6. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/setup.cfg +0 -0
  7. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli/__main__.py +0 -0
  8. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/SOURCES.txt +0 -0
  9. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/dependency_links.txt +0 -0
  10. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/entry_points.txt +0 -0
  11. {loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/top_level.txt +0 -0
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/PKG-INFO RENAMED
@@ -1,8 +1,8 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: loopsmith-cli
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`.
5
- Author-email: bitphill <bitphill@tuta.com>
5
+ Author-email: Vaibhav Agarwal <bitphill@duck.com>
6
6
  License-Expression: MIT
7
7
  Project-URL: Homepage, https://github.com/bitphill/loopsmith
8
8
  Project-URL: Repository, https://github.com/bitphill/loopsmith
@@ -21,7 +21,7 @@ Requires-Python: >=3.8
21
21
  Description-Content-Type: text/markdown
22
22
 
23
23
  <div align="center">
24
- <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
24
+ <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.2/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
25
25
  <h1>loopsmith</h1>
26
26
  <p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
27
27
  </div>
@@ -53,9 +53,10 @@ deterministic checker reads the actual files and decides — and it can revoke,
53
53
  a goal that stops being true stops being satisfied.
54
54
 
55
55
  **Not a developer?** Marketing, sales, research, ops — if you can edit a text
56
- file, you can run a loop.
56
+ file, you can run a loop. And if you would rather not open a text file at all,
57
+ `loopsmith --web` builds one for you in a browser.
57
58
 
58
- ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
59
+ ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.2/README-FOR-DUMMIES.md)
59
60
 
60
61
  A plain-English guide: one install line, thirteen ready-made loops to copy, the
61
62
  six settings you actually edit, and how to leave it running on a schedule.
@@ -78,6 +79,44 @@ One rule holds the whole design up:
78
79
  the gate can **revoke**: delete a required artifact and a satisfied goal flips
79
80
  back. A system that can only promote is a burndown chart with extra steps.
80
81
 
82
+ ## The browser UI
83
+
84
+ ```bash
85
+ loopsmith --web # or: loopsmith web
86
+ ```
87
+
88
+ Serves `http://127.0.0.1:3000` and opens a tab. Everything the CLI does, done by
89
+ clicking — with every field explained in place, for people who would rather not
90
+ learn a schema before they learn whether the tool is useful.
91
+
92
+ Six steps rather than one long form — Place, Power, Intent, Proof, Work, Ship —
93
+ carrying only the actions that make sense on each, and `⌘K` to reach any step,
94
+ section, action, or example directly.
95
+
96
+ It probes the machine first, so nothing has to be typed from memory: agent CLIs
97
+ on `PATH`, the Ollama models actually pulled, MCP servers already configured by
98
+ your editor, which API keys are set, and which sub-agents are installed. Found
99
+ CLIs become one-click provider cards prefilling a working argv, and a **Test**
100
+ button puts one real prompt through a provider so a wrong flag surfaces now
101
+ rather than in iteration four of an unattended run. The folder button opens your
102
+ operating system's own folder chooser, so no path has to be typed at all.
103
+
104
+ The right-hand panel re-checks the draft on every keystroke — the same validator,
105
+ planner, and permission derivation the CLI uses, in-process: every problem with
106
+ the field it belongs to, what a run could cost at the ceilings currently set (or
107
+ **unbounded** if none is), the wave schedule and the speedup ceiling no worker
108
+ count beats, and parallel builders that would overwrite each other.
109
+
110
+ All thirteen examples are compiled into the binary and load with one click. The
111
+ buttons spawn the real `loopsmith` binary and stream its output live, so the
112
+ browser can never drift from the CLI and can never do anything `loopsmith --help`
113
+ does not list. A run belongs to the server, not the page: close the tab and it
114
+ keeps going, reopen and the log picks up from the start.
115
+
116
+ Binds loopback only, and refuses any request not addressed to it. API keys go to
117
+ your shell profile or your OS secret store — only the variable *name* is ever
118
+ written into a config.
119
+
81
120
  ## Five minutes
82
121
 
83
122
  ```bash
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/README.md RENAMED
@@ -1,5 +1,5 @@
1
1
  <div align="center">
2
- <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
2
+ <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.2/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
3
3
  <h1>loopsmith</h1>
4
4
  <p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
5
5
  </div>
@@ -31,9 +31,10 @@ deterministic checker reads the actual files and decides — and it can revoke,
31
31
  a goal that stops being true stops being satisfied.
32
32
 
33
33
  **Not a developer?** Marketing, sales, research, ops — if you can edit a text
34
- file, you can run a loop.
34
+ file, you can run a loop. And if you would rather not open a text file at all,
35
+ `loopsmith --web` builds one for you in a browser.
35
36
 
36
- ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
37
+ ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.2/README-FOR-DUMMIES.md)
37
38
 
38
39
  A plain-English guide: one install line, thirteen ready-made loops to copy, the
39
40
  six settings you actually edit, and how to leave it running on a schedule.
@@ -56,6 +57,44 @@ One rule holds the whole design up:
56
57
  the gate can **revoke**: delete a required artifact and a satisfied goal flips
57
58
  back. A system that can only promote is a burndown chart with extra steps.
58
59
 
60
+ ## The browser UI
61
+
62
+ ```bash
63
+ loopsmith --web # or: loopsmith web
64
+ ```
65
+
66
+ Serves `http://127.0.0.1:3000` and opens a tab. Everything the CLI does, done by
67
+ clicking — with every field explained in place, for people who would rather not
68
+ learn a schema before they learn whether the tool is useful.
69
+
70
+ Six steps rather than one long form — Place, Power, Intent, Proof, Work, Ship —
71
+ carrying only the actions that make sense on each, and `⌘K` to reach any step,
72
+ section, action, or example directly.
73
+
74
+ It probes the machine first, so nothing has to be typed from memory: agent CLIs
75
+ on `PATH`, the Ollama models actually pulled, MCP servers already configured by
76
+ your editor, which API keys are set, and which sub-agents are installed. Found
77
+ CLIs become one-click provider cards prefilling a working argv, and a **Test**
78
+ button puts one real prompt through a provider so a wrong flag surfaces now
79
+ rather than in iteration four of an unattended run. The folder button opens your
80
+ operating system's own folder chooser, so no path has to be typed at all.
81
+
82
+ The right-hand panel re-checks the draft on every keystroke — the same validator,
83
+ planner, and permission derivation the CLI uses, in-process: every problem with
84
+ the field it belongs to, what a run could cost at the ceilings currently set (or
85
+ **unbounded** if none is), the wave schedule and the speedup ceiling no worker
86
+ count beats, and parallel builders that would overwrite each other.
87
+
88
+ All thirteen examples are compiled into the binary and load with one click. The
89
+ buttons spawn the real `loopsmith` binary and stream its output live, so the
90
+ browser can never drift from the CLI and can never do anything `loopsmith --help`
91
+ does not list. A run belongs to the server, not the page: close the tab and it
92
+ keeps going, reopen and the log picks up from the start.
93
+
94
+ Binds loopback only, and refuses any request not addressed to it. API keys go to
95
+ your shell profile or your OS secret store — only the variable *name* is ever
96
+ written into a config.
97
+
59
98
  ## Five minutes
60
99
 
61
100
  ```bash
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/pyproject.toml RENAMED
@@ -6,12 +6,12 @@ build-backend = "setuptools.build_meta"
6
6
  # `loopsmith` on PyPI was already registered by an unrelated project, so the
7
7
  # distribution is `loopsmith-cli`. The installed command is `loopsmith`.
8
8
  name = "loopsmith-cli"
9
- version = "0.2.0"
9
+ version = "0.2.2"
10
10
  description = "Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`."
11
11
  readme = "README.md"
12
12
  license = "MIT"
13
13
  requires-python = ">=3.8"
14
- authors = [{ name = "bitphill", email = "bitphill@tuta.com" }]
14
+ authors = [{ name = "Vaibhav Agarwal", email = "bitphill@duck.com" }]
15
15
  keywords = ["agent", "loop", "llm", "orchestration", "cli", "rust"]
16
16
  classifiers = [
17
17
  "Development Status :: 4 - Beta",
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli/__init__.py RENAMED
@@ -25,7 +25,7 @@ import urllib.request
25
25
  import zipfile
26
26
  from pathlib import Path
27
27
 
28
- __version__ = "0.2.0"
28
+ __version__ = "0.2.2"
29
29
 
30
30
  REPO = "bitphill/loopsmith"
31
31
  _RELEASE_BASE = f"https://github.com/{REPO}/releases/download/v{__version__}"
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/src/loopsmith_cli.egg-info/PKG-INFO RENAMED
@@ -1,8 +1,8 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: loopsmith-cli
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Summary: Self-evolving agent loops behind a deterministic verification gate. Installs the prebuilt Rust binary as `loopsmith`.
5
- Author-email: bitphill <bitphill@tuta.com>
5
+ Author-email: Vaibhav Agarwal <bitphill@duck.com>
6
6
  License-Expression: MIT
7
7
  Project-URL: Homepage, https://github.com/bitphill/loopsmith
8
8
  Project-URL: Repository, https://github.com/bitphill/loopsmith
@@ -21,7 +21,7 @@ Requires-Python: >=3.8
21
21
  Description-Content-Type: text/markdown
22
22
 
23
23
  <div align="center">
24
- <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.0/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
24
+ <img src="https://raw.githubusercontent.com/bitphill/loopsmith/v0.2.2/assets/loopsmith-logo-256.png" alt="loopsmith" width="180" />
25
25
  <h1>loopsmith</h1>
26
26
  <p><em>Self-evolving agent loops. The gate is code, so "done" cannot be argued.</em></p>
27
27
  </div>
@@ -53,9 +53,10 @@ deterministic checker reads the actual files and decides — and it can revoke,
53
53
  a goal that stops being true stops being satisfied.
54
54
 
55
55
  **Not a developer?** Marketing, sales, research, ops — if you can edit a text
56
- file, you can run a loop.
56
+ file, you can run a loop. And if you would rather not open a text file at all,
57
+ `loopsmith --web` builds one for you in a browser.
57
58
 
58
- ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.0/README-FOR-DUMMIES.md)
59
+ ### ➜ [START-HERE — README-FOR-DUMMIES.md](https://github.com/bitphill/loopsmith/blob/v0.2.2/README-FOR-DUMMIES.md)
59
60
 
60
61
  A plain-English guide: one install line, thirteen ready-made loops to copy, the
61
62
  six settings you actually edit, and how to leave it running on a schedule.
@@ -78,6 +79,44 @@ One rule holds the whole design up:
78
79
  the gate can **revoke**: delete a required artifact and a satisfied goal flips
79
80
  back. A system that can only promote is a burndown chart with extra steps.
80
81
 
82
+ ## The browser UI
83
+
84
+ ```bash
85
+ loopsmith --web # or: loopsmith web
86
+ ```
87
+
88
+ Serves `http://127.0.0.1:3000` and opens a tab. Everything the CLI does, done by
89
+ clicking — with every field explained in place, for people who would rather not
90
+ learn a schema before they learn whether the tool is useful.
91
+
92
+ Six steps rather than one long form — Place, Power, Intent, Proof, Work, Ship —
93
+ carrying only the actions that make sense on each, and `⌘K` to reach any step,
94
+ section, action, or example directly.
95
+
96
+ It probes the machine first, so nothing has to be typed from memory: agent CLIs
97
+ on `PATH`, the Ollama models actually pulled, MCP servers already configured by
98
+ your editor, which API keys are set, and which sub-agents are installed. Found
99
+ CLIs become one-click provider cards prefilling a working argv, and a **Test**
100
+ button puts one real prompt through a provider so a wrong flag surfaces now
101
+ rather than in iteration four of an unattended run. The folder button opens your
102
+ operating system's own folder chooser, so no path has to be typed at all.
103
+
104
+ The right-hand panel re-checks the draft on every keystroke — the same validator,
105
+ planner, and permission derivation the CLI uses, in-process: every problem with
106
+ the field it belongs to, what a run could cost at the ceilings currently set (or
107
+ **unbounded** if none is), the wave schedule and the speedup ceiling no worker
108
+ count beats, and parallel builders that would overwrite each other.
109
+
110
+ All thirteen examples are compiled into the binary and load with one click. The
111
+ buttons spawn the real `loopsmith` binary and stream its output live, so the
112
+ browser can never drift from the CLI and can never do anything `loopsmith --help`
113
+ does not list. A run belongs to the server, not the page: close the tab and it
114
+ keeps going, reopen and the log picks up from the start.
115
+
116
+ Binds loopback only, and refuses any request not addressed to it. API keys go to
117
+ your shell profile or your OS secret store — only the variable *name* is ever
118
+ written into a config.
119
+
81
120
  ## Five minutes
82
121
 
83
122
  ```bash
{loopsmith_cli-0.2.0 → loopsmith_cli-0.2.2}/setup.cfg RENAMED
File without changes