brainfile
The Python engine behind Brainfile.
This library provides the core logic for managing Brainfile v2 projects: reading/writing task files, managing contracts, validating boards, and querying task state. It is the Python equivalent of @brainfile/core with full API parity.
Used by Cecli and other tools that need programmatic access to Brainfile workspaces.
Installation
pip install brainfile
Or with uv:
uv add brainfile
To enable file watching (optional):
pip install brainfile[watch]
v2 Architecture
Brainfile v2 uses a directory-based structure. Each task is its own markdown file.
.brainfile/
├── brainfile.md # Board config (columns, types, rules)
├── board/ # Active tasks
│ ├── task-1.md
│ └── task-2.md
└── logs/ # Completed tasks (history)
└── task-0.md
Quick Start
from brainfile import ensure_dirs, add_task_file, read_tasks_dir, complete_task_file
# Initialize workspace
dirs = ensure_dirs(".brainfile/brainfile.md")
# Add a task
result = add_task_file(
dirs.board_dir,
{"title": "Implement auth", "column": "in-progress", "priority": "high"},
body="## Description\nAdd JWT authentication to the API.\n",
)
print(result["task"].id) # "task-1"
# List all active tasks
for doc in read_tasks_dir(dirs.board_dir):
t = doc.task
print(f"{t.id}: {t.title} [{t.column}]")
# Complete a task (moves to logs/)
complete_task_file(result["file_path"], dirs.logs_dir)
Task File Operations
Read and write individual task files.
from brainfile import read_task_file, write_task_file, find_workspace_task, get_dirs
# Read a single task
doc = read_task_file(".brainfile/board/task-1.md")
print(doc.task.title)
print(doc.body) # Markdown content below frontmatter
# Find a task across board and logs
dirs = get_dirs(".brainfile/brainfile.md")
result = find_workspace_task(dirs, "task-1", search_logs=True)
if result:
print(result["doc"].task.title, "in", "logs" if result["is_log"] else "board")
Contracts
Tasks can carry formal contracts for AI agent coordination: deliverables, validation commands, constraints, and feedback for rework.
from brainfile import read_task_file, write_task_file, Contract, Deliverable
doc = read_task_file(".brainfile/board/task-1.md")
task = doc.task
# Attach a contract
task.contract = Contract(
status="ready",
deliverables=[
Deliverable(path="src/auth.py", description="JWT auth module"),
Deliverable(path="tests/test_auth.py", description="Unit tests"),
],
validation={"commands": ["pytest tests/test_auth.py"]},
constraints=["Use PyJWT library", "Token expiry must be configurable"],
)
write_task_file(".brainfile/board/task-1.md", task, doc.body)
Contract Lifecycle
ready → in_progress → delivered → done
│ │
└─────────→ failed ←────┘
(add feedback, reset to ready)
File Discovery
from brainfile import discover, find_nearest_brainfile, is_workspace
# Find brainfiles in a project
result = discover("/path/to/project")
for f in result.files:
print(f"{f.name}: {f.item_count} tasks")
# Walk up to find nearest brainfile
path = find_nearest_brainfile()
# Check if a workspace has the v2 board/ directory
if is_workspace(".brainfile/brainfile.md"):
print("V2 workspace detected")
Ecosystem
| Package | Description |
|---|---|
| brainfile (Python) | This library |
| @brainfile/core | TypeScript core library |
| @brainfile/cli | CLI with TUI and MCP server |
| Protocol | Specification and JSON Schema |
Development
git clone https://github.com/brainfile/py.git
cd py
uv sync --dev
uv run pytest
License
MIT
Metadata
Release files for brainfile 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| brainfile-0.4.0.tar.gz | 97.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| brainfile-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 143.7 kB
Release files / brainfile-0.4.0.tar.gz
| Download URL | brainfile-0.4.0.tar.gz |
|---|---|
| Size | 97.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffbb560bd50b7e56d551f9a985eef530c1541e19a934d122bc788c653917de95
|
|
BLAKE2b-256 checksum How to use checksums |
48478b9b52a49b643efeaf288c1d59d95af73e73669d203e4944de316914e7ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logRelease files / brainfile-0.4.0-py3-none-any.whl
| Download URL | brainfile-0.4.0-py3-none-any.whl |
|---|---|
| Size | 46.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b99b94d5389b11dfe11bbc8ee7e5918e15f88fab33dd511b62c1fb5e8beb4a5
|
|
BLAKE2b-256 checksum How to use checksums |
a97ebb72dba9266a9bfeb9714cf5889012a0f9808a4a40c4c09c3912b7a54b79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency log