In developmentBlink is in active development and not yet publicly released. Command snippets are illustrative previews of the intended interface, not captured output.

Docs

Configuration

Blink is configured through a single native project file: .bnk.

Every project can carry a .bnk file in its root. It tells Blink how the project works — its name, the commands you run, and what to skip when scanning and indexing.

.bnk
# .bnk
[project]
name = "my-app"

[commands]
dev = "npm run dev"
test = "npm test"

[scan]
ignore = ["node_modules"]

The file is optional. Without it, Blink falls back to what it can detect on its own. With it, every contributor gets the same Blink behavior because the file is committed alongside the code.

What you can configure

  • Customize analysis
  • Define project commands
  • Configure indexing
  • Manage workflows
  • Support plugins

For the full field-by-field breakdown, see the .bnk reference.