sphica 0.6.65 → 0.6.66

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
3
3
  "name": "sphica",
4
- "version": "0.6.65",
4
+ "version": "0.6.66",
5
5
  "description": "Records Claude Code and Codex sessions on your machine and keeps past implementation and decisions, with their sources, for your agent to find.",
6
6
  "author": {
7
7
  "name": "iroha924",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sphica",
3
- "version": "0.6.65",
3
+ "version": "0.6.66",
4
4
  "description": "Records Claude Code and Codex sessions on your machine and keeps past implementation and decisions, with their sources, for your agent to find.",
5
5
  "author": {
6
6
  "name": "iroha924",
package/README.md CHANGED
@@ -83,6 +83,20 @@ codex plugin add sphica@sphica
83
83
 
84
84
  In Codex, open `/hooks` and mark Sphica's hooks as trusted. Automatic recording does not start until you do. If a plugin update changes the hooks, trust them again. The "Codex hooks" line of `sphica doctor` shows how many are trusted (for Codex 0.160.0).
85
85
 
86
+ Optional, Claude Code only: a pane that lists what Sphica handed the agent in this session.
87
+
88
+ ```bash
89
+ claude plugin install sphica-pane@sphica
90
+ ```
91
+
92
+ Run `/sphica-pane` to open it, and press ctrl+x then x to close it. Newest first, it shows the current work and constraints given at session start, the records given before a read, an edit, or a prompt, and the reason when Sphica stopped a shell call.
93
+
94
+ - It needs Claude Code 2.1.300 or later, the version its checks run on. Older Claude Code fails to load it, and Sphica itself keeps working.
95
+ - It is a Claude Code mod, so it runs with Claude Code's permissions. It only reads what the hooks returned and passes that on unchanged. It writes nothing, reads no files, and sends nothing anywhere.
96
+ - It recognizes Sphica's text by its wording, so text another plugin writes in the same words shows too. Treat it as a view, not a record.
97
+ - Where an organization manages Claude Code, the hooks it reads run only for plugins the organization lists, so the pane stays empty.
98
+ - Codex has no mods. `codex plugin list` shows sphica-pane too, but do not install it there: Codex warns about its hooks file in every session.
99
+
86
100
  **3. Set up in your repository**
87
101
 
88
102
  ```bash
@@ -193,6 +207,8 @@ claude plugin marketplace update sphica
193
207
  claude plugin update sphica@sphica
194
208
  ```
195
209
 
210
+ If you installed the pane, update it too with `claude plugin update sphica-pane@sphica`. A fix to it comes with the next Sphica release.
211
+
196
212
  Codex:
197
213
 
198
214
  ```bash
@@ -216,6 +232,8 @@ codex plugin remove sphica@sphica && codex plugin marketplace remove sphica
216
232
  npm uninstall -g sphica
217
233
  ```
218
234
 
235
+ If you installed the pane, remove it first with `claude plugin uninstall sphica-pane@sphica`. Removing the pane alone leaves Sphica working.
236
+
219
237
  ## Troubleshooting
220
238
 
221
239
  Run `sphica doctor` first. It shows which part is out of date or not working. Common cases:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sphica",
3
- "version": "0.6.65",
3
+ "version": "0.6.66",
4
4
  "description": "Records Claude Code and Codex sessions on your machine and keeps past implementation and decisions, with their sources, for your agent to find.",
5
5
  "license": "MIT",
6
6
  "type": "module",