ignore

Overview ¶

Package ignore is a gitignore-style agent read filter.

Users can point vibekit at one or more ignore files (.gitignore, .kiroignore, etc.). Any read path that matches the combined patterns is refused by the fs/read_text_file handler. Writes are NOT affected — matches git's semantics where ignored files are writable, just not tracked. The intent is to stop the agent from slurping decrypted secrets (`.env.dec`), build artifacts, and other files the user deliberately excluded from version control into its context window.

Supported gitignore features (subset):

• Literal paths ("node_modules").
• Globs: `*`, `?`, and `**` (matches across directory boundaries).
• Leading `/` anchors to the ignore file's directory — "/node" matches only a top-level "node" entry, not "src/node".
• Trailing `/` restricts the rule to directories.
• Directory-match implies descendants: "/secrets" matches "secrets" AND "secrets/api.key" AND "secrets/sub/deep.json" (standard gitignore semantics).
• Leading `!` negates a previously-matched rule so users can carve out exceptions ("!/.env.example").
• `#` comments; blank lines ignored.

Supported via filepath.Match: character classes (`[abc]`, `[a-z]`, `[^abc]`). Not supported (deliberately): backslash escapes and the full git `!` re-inclusion semantics that depend on whether the parent directory was itself ignored. If we need those we'll rebuild against go-gitignore later.

Matcher is case-sensitive and operates on slash-separated paths (matching what resolveInsideWorkDir produces).

Fail mode: a transient config.json read/parse failure (oversized, corrupt JSON, wrong-type list) clears the in-memory ruleset, effectively disabling the matcher (fail-open) until the next successful read. The alternative — fail-closed block-all — would lock the agent out of the workspace on any disk blip. Errors are logged at slog.Warn so transient failures are visible in Loki. A persistently broken config.json surfaces as a one-time warn plus all-permissive matches until fixed.