paragma 0.3.6 → 0.4.0
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.
- package/README.md +6 -2
- package/SHA256SUMS +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -126,6 +126,8 @@ pg setup
|
|
|
126
126
|
|
|
127
127
|
In scripts: `pg setup codex --global`, `pg setup claude --dir .`, `pg setup all --global`, `pg setup --list`.
|
|
128
128
|
|
|
129
|
+
**MCP.** Apps that start MCP servers can run Paragma as one: the app gets the project's brief when a conversation starts and pg's commands as tools, which helps most in apps without a shell or hooks. In `pg setup` choose **MCP** and an app (Claude Code, Claude Desktop, Codex, Antigravity, Cursor; for every conversation), or `pg setup all --mcp`; `--no-mcp` takes it out. Where Paragma's hooks already give the brief, the server does not repeat it.
|
|
130
|
+
|
|
129
131
|
## Commands
|
|
130
132
|
|
|
131
133
|
The section `pg setup` writes is short: when to call `pg`. The details are in three skills the agent reads when it needs them (`pg skill coding`, `pg skill projects`, `pg skill knowledge`, also kept as files in `~/.paragma/skills/`), and `pg <command> --help` explains every option.
|
|
@@ -142,14 +144,15 @@ pg write --decision "..." --why "..." --alternatives "..."
|
|
|
142
144
|
pg write --error "<error line>" --cause "..." --fix "..."
|
|
143
145
|
pg write payments/provider --file notes.md # a note; long text from a file or stdin (-)
|
|
144
146
|
pg finish --done 1 "what changed, what is next" # tick off steps, leave the handoff
|
|
145
|
-
pg steps # the steps with their numbers (--defer 4, --drop 4, --edit 4 "text")
|
|
147
|
+
pg steps # the steps with their numbers (--take 4, --defer 4, --drop 4, --edit 4 "text")
|
|
148
|
+
pg tell "I am changing refund.go" # a note the other conversations on the project see once
|
|
146
149
|
pg ask "Which address on invoices?" # a question that waits on the user; the brief lists it until pg answer 1 "..."
|
|
147
150
|
pg ripple # what a change reaches: callers left as they were, tests to run
|
|
148
151
|
pg tree # the code: files and symbols, with the notes about them marked
|
|
149
152
|
pg ls # projects, or the notes of one; also pg mv, pg rm, pg doctor
|
|
150
153
|
```
|
|
151
154
|
|
|
152
|
-
Many `pg` calls can run at once, from several conversations. `pg rm` moves notes to `.archive/` instead of deleting them.
|
|
155
|
+
Several conversations on one project see each other: who is at work, the steps another has taken, the notes they left, and what a conversation that stopped without a handoff did. Many `pg` calls can run at once, from several conversations, on one project or many. A write is whole or not there at all, also when its process is killed halfway. `pg rm` moves notes to `.archive/` instead of deleting them. pg's own index files are made again from the notes when they are damaged (kept aside as `.broken`); `pg doctor` also looks for damage deep inside them.
|
|
153
156
|
|
|
154
157
|
### Secrets
|
|
155
158
|
|
|
@@ -182,6 +185,7 @@ Run `pg git` again to see the account, the repository and the last sync, to chan
|
|
|
182
185
|
- **What a change reaches.** `pg ripple` compares the code with the last commit: a function whose signature changed, renamed or removed, with the callers the change left as they were and the tests that reach it; a shader struct, GraphQL or Protobuf type or SQL table whose fields changed, with the other code that names them. `pg run`, the hooks and `pg finish` say it by themselves; `pg ripple Refund` tells what reaches a function before changing it.
|
|
183
186
|
- **Libraries at their versions.** The libraries a project locks (Cargo.lock, node_modules, go.mod, a virtual environment) are read from the source already on the computer, when an agent asks: `pg find "serde_json Value get"` gives the real signature, doc, example, the feature it needs and deprecation at that version; a failed build that looked for a name a library does not have gets the right one from `pg run`; an upgrade is pointed out in the brief with what changed in what the code calls.
|
|
184
187
|
- **Records that merge.** Writing a rule, decision or error that is already known updates the existing one instead of adding a copy; a decision that contradicts an earlier one is pointed out.
|
|
188
|
+
- **A pure core.** What pg says is decided by a kernel that reads only facts (the event log, the runs, what was already said) and never a file or the clock: small experts each notice one thing (a conversation cut short, the commands that work, a note whose code is gone, notes that could be tidier), and attention chooses what fits the agent's context, never twice. Each kind of hint is weighted by how often agents acted on it; a note fades by its uses (ACT-R). Heavy looks over the whole memory run after `pg finish`, in the background.
|
|
185
189
|
- **One binary.** `pg` is written in Rust: no runtime, no server, and no network unless you connect `pg git` (it uses git and curl). The indexes next to the notes can be deleted at any time and are rebuilt.
|
|
186
190
|
|
|
187
191
|
## How it is tested
|
package/SHA256SUMS
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
110c06f4ab05f85ed3bcd1160003d2239bbe248856edd705a2fc729018f6586f pg-darwin-arm64
|
|
2
|
+
be9f131472dcacd899401d524007f71013d8c5012edc246194752d697b9fafc8 pg-darwin-x64
|
|
3
|
+
d5484666f1a767bb7891f7cface127884dc1c1eb2b487fd98e20cffef80f81fe pg-linux-arm64
|
|
4
|
+
bf142075e064fc6ce03084061172d1358e4a39e1c188aff095c461d5dc4f6707 pg-linux-x64
|
|
5
|
+
b4ea9db208c27535556136894afac40b429d5402382a4d8d11435c1d545fd93d pg-windows-arm64.exe
|
|
6
|
+
28f84f0d3d16e45ba601fad0cc125163e436899229eff880579445ee9984c49f pg-windows-x64.exe
|
package/package.json
CHANGED