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

Docs

The Blink Project File

.bnk lets Blink understand how your project works.

Why .bnk exists

Blink can detect a great deal about a project on its own, but no detector knows the specific commands your team runs or the paths you want ignored. .bnk is where you tell Blink those things once, in a file that lives in the repository and travels with it.

A .bnk file

.bnk

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

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

[scan]
ignore = ["node_modules"]

Reference

Table	Key	Type	Description
[project]	name	string	The project's name. Shown in Blink's output.
[commands]	<name>	string	Named workflow commands, e.g. dev = "npm run dev". Run them with blink run <name>.
[scan]	ignore	string[]	Paths to exclude from inspection and indexing, e.g. ["node_modules"].

What makes it different

Optional

Blink works without it. Add a .bnk only when you want to shape how Blink reads your project.

Lightweight

A small, readable file that lives in your repository root — no scaffolding, no ceremony.

Language independent

The same format works whether your project is Rust, TypeScript, Python, or a mix.

Project specific

Committed alongside your code, so every contributor gets the same Blink behavior.