Repository navigation
Releases: bleak-ai/gcontext
Release list
gcontext v0.15.0
-
gcontext statusline command: one line for your client statusline. Green "gcontext ok" when current, amber "RECONNECT NEEDED FOR --> /new_cmd , -removed_cmd" when the client is behind, "STALE" for hand edits, "down" when the server is not running. --color flag for ANSI colors.
-
Server self-reload: edits made through the MCP tools (write_file to commands, controls.yaml, agent.md; agent install/update) apply without running gcontext reload.
-
/status reports client_behind: whether the connected client misses commands or an agent.md change, and which.
-
Dashboard banner when the client needs a reconnect, with the exact items.
-
.gcontext-port lockfile so CLI subcommands find the running server's port.
-
Dashboard copy buttons produce plain gcontext://path references.
-
Console warnings for hand edits now say "changed outside tools; run gcontext reload".
gcontext v0.14.0
Changed
- Controls tab redesigned: sticky header with server name and connected status, search with "/" shortcut, All/Listed/Hidden segmented filter, Resources/Commands type chips, Descriptions toggle, collapsible sections with white group cards, List all/Hide all bulk actions, inline copy and rename, fixed pending-changes bar with Discard/Reload, green reloaded toast
- Commands tab removed (now redundant with Controls)
- Backend adds category field to command rows for grouped display
Fixed
- Pin POST validates that the target file exists on disk and rejects path traversal attempts
Docs
- README: added dashboard mention, registry links to gcontext.ai/agents, documented gcontext remove, clarified uv/Python prereqs
- using.md: explained setup command naming convention
- CLI: fixed add help example (browser-recipes to browser-cookbook)
gcontext v0.13.1
Added
- agents/ folder parity: MCP resource picker, root resource map, ask/explain/setup prompts, context ledger, dashboard, CLI banner, restart notes, and docs now treat agents/ equal to connections/ and modules/
- controls.yaml as full on/off registry with one-time migration from the old auto values
- Controls tab in dashboard: toggle, rename, bulk-toggle, flat layout with reload banner
- File pinning in dashboard Files tab
- gcontext reload replaces the three-step restart cycle in framework instructions
- New docs: using.md, mcp.md, tools.md, troubleshooting.md
Changed
- names: section in controls.yaml renames commands and resource display titles
- Legacy dual-scan removed: agents scan only agents/, no longer fall back to modules/
Removed
- Auto value in controls.yaml (migrated to explicit on/off)
gcontext 0.12.2
Added
controls.yaml: single file to control the MCP surface (replacescommands.yaml, breaking)hidden_commands: hide slash commands by stable keyhidden_resources: hide modules/connections from the resource picker (fnmatch globs supported)pinned_resources: surface specific files in the resource picker
Fixed
- Manifest loads before framework prompt registration so
hidden_commandsapplies to built-in prompts
gcontext 0.12.1
Added
- Command control:
commands.yamlwith adisabledlist lets you hide any command by its stable key (e.g.browser-cookbook/browse) sharesandconfigurablefields in the agent manifest, with validation on install and share- Dashboard agents tab and
/api/agentsendpoint - Startup log shows how many commands are disabled
Changed
- Connection scaffolding reports missing kinds instead of creating stub folders
- Update flow is ownership-aware: learned directories are skipped, configurable files backed up as
.pre-update, example runs skipped when real runs exist
Fixed
- Hash comparison strips injected base-path comments so check/update reports match the registry
gcontext v0.11.0
-
13 new tests: dashboard command name verification, parse_github_url unit tests, secrets.scrub edge cases (254 total).
-
agent tool added to framework instructions (tool count corrected from 6 to 7).
-
Dashboard command names match the server's registered prompt names (copy button works).
-
GCONTEXT_REGISTRY @ref supports tags and SHAs, not just branches.
-
run_adhoc_script writes temp files to .venv/ instead of the project root.
-
.venv-sync.lock hidden from agent-visible listings.
-
CLI: port parsing error is friendly, cmd_add error dispatch is specific, cmd_init drops duplicate output.
-
Example ops-agent follows portability conventions (payment provider not stripe).
-
run_script blocks execution of secrets.env (security fix).
-
Dead prompts/resources.md and stale resource template comment.
-
Dead api/scripts/seed.py and duplicate _available_kinds function.
v0.10.3
Added
- Connection scaffolding: gcontext add now creates connections// stubs from the module's declared connections, with connection.yaml and index.md pre-filled
- Configurable timeout on run_script and run_adhoc_script (default 60s, max 600s)
- Connection schema (all 5 fields, all 8 kind values) documented in the framework instructions pushed to clients on connect
- Prompt-less client fallback: instructions now explain how to use commands in clients that do not surface MCP prompts
Fixed
- SSL failures on fresh macOS installs (certifi added as explicit dependency)
- Venv sync no longer runs uv pip install on every exec call when deps have not changed (marker cache)
- Exec channel no longer wedges when another call is installing deps (sync lock with structured busy error)
- Timed-out scripts now kill the entire process group, not just the direct child (prevents orphaned browser processes)
- Root README.md excluded from agent installs and validation
Changed
- README rewritten; detailed sections moved to docs/reference.md
v0.10.1
Added
- index_format_issues() validator: checks that every index.md follows the expected shape (title, summary, bullets, sibling coverage)
- gcontext share hard-rejects agents with malformed index.md files before publish
- 16 new tests for the index format validator
Fixed
- Substring bug in _mentions() that could match partial filenames as referenced siblings
- write_file warning message now explains the expected index.md shape so the agent can self-correct
v0.10.0
-
Generated commands: a command file with each: registers one slash command per matching state folder, e.g. one command per saved recipe. New entries appear at runtime after a client reconnect; a parameter default makes its argument optional.
-
Agent dependencies: a manifest can declare agents: with registry ids; install resolves them recursively and reports each one.
-
explain prompt: a what-is-this-agent walkthrough built from the instance's real state.
-
Setup script standard: setup and install texts follow one spec, with code-built reports shown verbatim; the share validator enforces it.
-
Commands register under short names: /mcp__save_recipe instead of /mcp____save_recipe. The owner prefix returns only when two commands collide or a name is reserved by the framework.
-
CLI banners follow the script standard; agent-facing wording lives in markdown prompt files, not Python strings.
-
The templates/ folder: the bleak-ai/agents registry is the single source of installable agents.
-
Dev checkouts no longer send install telemetry pings.
gcontext 0.9.0
Changed
- The installable unit is now called an agent. Install with
gcontext add <agent-id>from the bleak-ai/agents registry. - The MCP tool
workflowis renamed toagent. Clients that call the old name must switch. - Agent manifests support two new optional fields:
connections[].examplesandlearns. - The setup prompt now checks installed agents first: if an agent's declared connections are missing, it reports which agents are not operational and offers to build those connections before anything new.