@aistastudio/myc 0.3.5 → 0.3.6
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 +22 -5
- package/dist/myc.js +525 -517
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -31,7 +31,7 @@ Installation is one command:
|
|
|
31
31
|
|
|
32
32
|
```bash
|
|
33
33
|
bun install -g @aistastudio/myc # 3.20 MB, 10 files, no models pulled at install
|
|
34
|
-
myc --version # myc 0.3.
|
|
34
|
+
myc --version # myc 0.3.6 (schema 1)
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
It runs on macOS and Linux; on Windows, use WSL.
|
|
@@ -82,10 +82,27 @@ Before anything else the helper checks, without starting myc, whether there is
|
|
|
82
82
|
a workspace here (a git worktree is resolved through its main copy), and stays
|
|
83
83
|
silent when there is none or the project wires myc itself: in a project without
|
|
84
84
|
myc the hook costs one node start, and prime never arrives twice. Outside a
|
|
85
|
-
workspace the MCP server offers zero tools and no instructions.
|
|
86
|
-
`
|
|
87
|
-
|
|
88
|
-
|
|
85
|
+
workspace the MCP server offers zero tools and no instructions. `--hook-mode
|
|
86
|
+
replace` is refused here. The journal is `~/.myc/wire-user.json`; `myc unwire
|
|
87
|
+
--scope user` restores the settings node by node and removes the MCP server.
|
|
88
|
+
|
|
89
|
+
With `--status-line` the user layer also gets myc's status line, `myc
|
|
90
|
+
statusline --scope user`: in a myc workspace — a git worktree of one included —
|
|
91
|
+
it is the full line, outside one it prints nothing of its own. The line that was
|
|
92
|
+
there (orca's, which prints nothing and posts the input to orca) is kept in the
|
|
93
|
+
journal, not in our command, and gets the same stdin on every redraw, never
|
|
94
|
+
waited on: orca takes a line whose command mentions its
|
|
95
|
+
`agent-hooks/claude-statusline.sh` for its own and removes it when it
|
|
96
|
+
uninstalls (a foreign line it leaves alone), so ours never carries the word
|
|
97
|
+
`claude-statusline`. A
|
|
98
|
+
project with its own myc line keeps it, and that line hands the input to the
|
|
99
|
+
same recorded line. If another tool replaces the user line after wire, `myc
|
|
100
|
+
doctor --hooks` says so; `myc wire --scope user --status-line` puts ours back
|
|
101
|
+
and makes the new line the previous one, and `myc unwire --scope user` puts the
|
|
102
|
+
previous line back byte for byte. `myc doctor --hooks` checks the whole user
|
|
103
|
+
layer against the journal: myc's hook entries and rules still in
|
|
104
|
+
`~/.claude/settings.json`, the helpers exactly what this build writes (a stale
|
|
105
|
+
one is named with the build that wrote it), the status line, the MCP server.
|
|
89
106
|
|
|
90
107
|
## Heavy commands take turns
|
|
91
108
|
|