Insight Loom

@egistr/insight-loom is a conservative OpenCode plugin that turns significant completed work into local Markdown drafts. It observes session.idle events and writes only to the active worktree's docs/blog/ directory.

Features

• Opt-in drafting from meaningful idle-session signals such as changed files, tests, and implementation summaries.
• Local Markdown drafts, redacted evidence, and operation manifests under docs/blog/.
• Bounded, normalized, deduplicated input handling with recursion protection.
• Dry-run mode and a configurable minimum signal threshold.
• No publishing, network requests, credential access, shell-command execution, or direct skill/command invocation.

Installation and registration

Install the scoped package in the OpenCode project where the plugin should run:

npm install @egistr/insight-loom

Register the package name in that project's opencode.json:

{
  "plugin": ["@egistr/insight-loom"]
}

A safe CLI is included for setup and inspection. Use it to initialize a project or global config entry, check whether the plugin is configured, and remove only the exact @egistr/insight-loom entry:

npx @egistr/insight-loom init
npx @egistr/insight-loom status
npx @egistr/insight-loom doctor
npx @egistr/insight-loom uninstall --yes

The CLI defaults to the project-local opencode.json. Add --global to target ~/.config/opencode/opencode.json, or --path for an explicit file. For a local checkout, you can also register the built plugin file directly:

{
  "plugin": ["./node_modules/@egistr/insight-loom/dist/plugin.js"]
}

Configuration and safety

Drafting is disabled by default. Set OPENCODE_TECH_BLOG_ENABLED=1 to enable it; use 0 to disable it explicitly. Set OPENCODE_TECH_BLOG_DRY_RUN=1 for dry-run behavior. OPENCODE_TECH_BLOG_MIN_SIGNALS is optional and defaults to 2.

The plugin does not read credentials, make network requests, publish content, execute shell commands, or invoke OpenCode skills or commands. It rejects paths outside the active worktree and writes with temp-file-plus-rename and exclusive deduplication fingerprints. Inputs are treated as untrusted: they are bounded, redacted, normalized, and checked for recursion markers before persistence. These safeguards do not replace review of generated drafts.

Output and lifecycle

Each accepted operation produces one terminal result: drafted, ledger-only, rejected, guarded-rejection, partial-failure, or failure. Operation manifests under docs/blog/.ledger/operations/ link redacted source records, derived artifacts, and review/publication metadata. Publication is intentionally outside this plugin and requires a separate, human-directed workflow.

See the operational contract for the local layout, migration, rollback, compatibility, and exclusion details.

Development

The package requires Node.js 20 or newer. Run the following checks before submitting changes:

npm run build
npm test
npm run typecheck
npm run format
npm pack --dry-run

See CONTRIBUTING.md and skill/technical-blogging/SKILL.md for project guidance.

Importable entry points

• Plugin entry: @egistr/insight-loom
• Explicit subpath: @egistr/insight-loom/plugin