Agent context¶
The instructions file your agent reads at every step (e.g. CLAUDE.md) can be managed from the board
(/context, administrators only):
php artisan griglia:context import --file=CLAUDE.md # once: markdown → groups (##) and blocks
php artisan griglia:context export # the enabled blocks as markdown
php artisan griglia:context status
Each group and block has a switch; blocks can be multi-selected and enabled/disabled together, edited (Markdown
editor), added, deleted and reordered; a token estimate is shown. On the host, a small script writes the export
back to the instruction files: scripts/sync-context.py, shipped with the package (see the scripts
— CLAUDE.md and AGENTS.md, cron every minute). Token-saving switches live in Settings → Optimization.
Keeping the original files¶
The switch Generate instruction files from the board (top of /context, setting app.context_sync)
decides whether the host sync writes the generated files (on) or restores and leaves the original files alone
(off) — useful when you stop using the board: the originals apply again. Host scripts read it with
php artisan griglia:context enabled (prints 1/0).
Blocks generated by the board¶
Some blocks are written by the board itself from a setting and carry a key (context_blocks.key): today the
question level (question_level, Settings → How the agent works → Question level). On /context they show
generated from Settings and cannot be edited — change the setting and the block is rewritten in place, keeping
its switch and position; switch it off or delete it if you do not want it (it comes back at the next save).
griglia:context import keeps it too: a re-imported generated file is adopted (no duplicate), and a file without
it gets the block appended in its own group.