Skip to content

Integration: shared PreToolUse enforcement across parallel looms via ThumbGate #980

Description

@IgorGanapolsky

Proposal

iloom runs multiple Claude Code sessions in parallel with isolated worktrees. Each loom is isolated — but within each session, there's no enforcement on what the agent can do. If one loom goes rogue (force-push, mass delete, destructive DDL), iloom has no way to stop it mid-execution.

ThumbGate adds PreToolUse hook enforcement to every agent session. One npx thumbgate init per loom, and every tool call is evaluated against 33+ gate rules before execution.

Why this is especially valuable for iloom

Shared learning across looms: When one loom makes a mistake and gets a thumbs-down, the prevention rule propagates to ALL looms via ThumbGate's shared SQLite+FTS5 lesson database. The same mistake never happens in any parallel session.

Budget enforcement per loom: Each loom gets action count + time limits. A runaway loom can't burn infinite tokens — it hits the budget gate and stops.

Self-protection: The agent within a loom cannot disable its own governance, modify gate rules, or kill the ThumbGate process.

Integration pattern

# In each loom's setup:
npx thumbgate init --agent claude-code

ThumbGate auto-detects the Claude Code runtime and wires PreToolUse hooks. No config needed. The shared lesson DB means enforcement improves across all looms over time.

Features

  • 33 pre-action gates (block/approve/log)
  • Thompson Sampling for adaptive gate sensitivity
  • Compliance tags (NIST, SOC2, OWASP, CWE)
  • Budget profiles: strict (500 actions), guided (2000), autonomous (5000)
  • DPO export for fine-tuning

Open source, free CLI. Happy to build a first-class iloom adapter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions