filelinks v1.1.0

filelinks v1.1.0

Release date: 2026-05-31
Milestone: v1.1 AI agent integration

Highlights

• Added agent run policy support in core (trigger-only, trigger-or-affects) with staged trigger/affect coverage classification.
• Added provider architecture with Cursor as the first provider and typed runtime/startup/missing-key errors.
• Added filelinks check --run-agents for opt-in agent execution after normal violation reporting.
• Added prompt assembly context for agents (resolved prompt config, trigger staged diff, readable affected file contents).
• Expanded filelinks add wizard with:
  • optional global/per-link agent + prompt setup,
  • live model discovery + fallback options,
  • model variant labels (default, Standard, Fast, etc.),
  • debounced model search in picker.
• Added Cursor API key precedence for CLI agent runs and model discovery:
  • --cursor-api-key (where supported),
  • CURSOR_API_KEY environment variable,
  • .env.local / .env under the effective --cwd.

User-facing changes

filelinks check

• New flag: --run-agents
• JSON mode now includes optional agentRuns summaries when agents are executed.
• Agent run policy default is trigger-only unless overridden in config.

filelinks add

• Interactive model picker now supports:
  • sorted model/variant lists,
  • meaningful labels focused on deltas from default presets,
  • input filtering with debounce for large model catalogs.

Config additions

agent config now supports:

• runPolicy
• provider
• runtime (local / cloud)
• model
• modelParams (variant params from model picker)
• local.cwd
• cloud.repos

Notes

• Cursor is the only provider implemented in v1.1.
• Existing check violation behavior and exit-code semantics remain intact.
• filelinks add remains interactive-only (no --json mode).

filelinks v1.0.0 — MVP (core + CLI)

Description

Milestone: v1.0.0 MVP — shipped per GSD (4 phases, 7 plans; archived 2026-04-06).

What filelinks is
Declare semantic relationships between files in a repo (any language). When a trigger changes, you get a clear signal about affected companions that should be reviewed or updated—without relying only on same-language import graphs.

Shipped in v1.0

• @filelinks/core — defineLinks, filelinks.config.ts loaded with jiti (walk-up from cwd), Effect Schema for public config shapes, typed errors (FilelinksError + normalizeError), git staged paths, minimatch link matching, optional linkType (file-file | dir-dir | file-dir | dir-file), resolvePrompt for global + per-link prompt merge (for future tooling).
• filelinks CLI — check (staged paths vs links; warn/error by severity), list, interactive add (Ink + React), global --cwd, optional --config, --json on check / list, publishable bin for npx filelinks after publish.
• Docs & contributor path — Root README for install and basic usage; CONTRIBUTING.md, AGENTS.md, architecture notes under .planning/codebase/; Husky + lint-staged + tests as in repo.

Intentionally not in v1.0 (tracked for later milestones)
AI suggest, shipped @filelinks/git-hook, graph, VS Code extension, Nx plugin—see archived v2 section in .planning/milestones/v1.0-REQUIREMENTS.md.

Traceability
Requirements CORE-01–CORE-09, CLI-01–CLI-04, DOC-01–DOC-02 in the v1.0 requirements archive; roadmap phases 01–04 in .planning/milestones/v1.0-ROADMAP.md.