Repository navigation
Conversation
…eps, and the hooks page names the local commands Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
… outbound calls, the full repository identity, the exact Python probe and what temp files keep Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
…e.json read, the issue's full report, agent-mode token storage and the active virtualenv, and its links are tested Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog category (leave one):
Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):
...
Why
The Claude Code plugin's README only linked data handling as
../../docs/features/integrations/claude-code.md#data-handling. That link breaks for anyone who installs the plugin folder alone, which is what a plugin directory serves, and a reader of the README had no statement of what the plugin sends, runs or keeps. The README now has a## Data handlingsection that says it in one place: what goes to the configured Loom server, which local commands the hooks run, what stays on the machine and for how long, which two skills reach other services and when (on Linuxloom-statusruns NodeSource's setup script orapk add nodejsas root or with passwordless sudo; on macOS it runs Homebrew as the user), that the server passes text to an LLM or embedding provider only if its operator configured one, that a user-scopeloomMCP entry beside the plugin registers a second server, and that SessionStart reads~/.claude.jsonlocally to warn about one. The agent-mode token's file and the public issue's full contents are named too. The full list stays on the docs page, now linked with an absolute URL, as is the MCP clients link.The hooks page's "What the hooks do" now names the local commands too:
node,git(remotes, branch, status, diffs),grepfor a redirected grep pattern, and, at Stop in an indexed checkout when the test gate names a pytest test and neither the checkout's virtualenv nor an active one exists,python3 -c "import pytest"(thenpython) to see whether pytest is installed (LOOM_TEST_GATE=off). The README's remaining links that pointed outside the plugin folder (requirements, Codex) are absolute now.Each item was checked against the plugin on
main: the session-memory hand-off (hooks/loom-session-memory.mjs,LOOM_SESSION_MEMORY=off), the local grep (lib/code-shunt.mjsrunLocalGrep), the test gate (hooks/loom-test-gate.mjs,LOOM_TEST_GATE), the agent-mode exchange (LOOM_CLIENT_ID,hooks/HOOKS.md), the shunt log (LOOM_SHUNT_LOG, kept out of the temp sweep inlib/tmp-state.mjs) and the two skills' outside calls, as the Data handling section ofdocs/features/integrations/claude-code.mdlists them.Scope and risk
Docs only:
integrations/claude-code-plugin/README.mdanddocs/features/integrations/claude-code.md. No hook, lib, bin, skill or manifest changes, so no plugin version bump.Compatibility, rollout and rollback
Tests
tests/unit/test_published_links.pynow reads the plugin README too, and checks itsgithub.com/ClickHouse/loom/tree/main/...folder links as well as its site links, since a plugin directory serves this README alone.tests/unit/test_doc_links.py,test_public_copy.py,test_agent_instructions.py,test_published_links.py: 448 passed.node --test integrations/claude-code-plugin/tests/*.test.mjs: 609 passed.check_prose.pyflags only four lines already onmain(/opt/homebrew,/opt/localpaths in install notes).AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated (an agent wrote most of the diff): Claude Code wrote the section from the plugin's data-handling docs and checked each item against the plugin code.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist
make format-check,make lint,make typecheckandmake test-unitpass; the integration suite passes if server behaviour changed. (Docs only: ran the doc and plugin tests above; CI runs the rest.)docs/describe the system as it now is, and this description names any operator steps and wire changes.tests/unit/test_public_copy.py).git commit -s), as CONTRIBUTING.md asks.🤖 Generated with Claude Code