Redux gave components shared state between renders. gcontext gives agents shared state between sessions.
gcontext is an MCP server that gives you access to a structured standard of plain text files and folders that helps you store any kind of information. Connections, modules, scripts, and decisions accumulate over time, so you can load it into a session.
You can add agents to your gcontext instance. These live locally in your machine or self-hosted platform to help you with any action you need.
A browser agent that learns your sites. It performs browser tasks through your real Chrome, accumulates per-site knowledge, and crystallizes repetitive tasks into plain Python scripts; on later runs the AI only dispatches the script and heals failures. Broken knowledge heals itself; blockers like captchas escalate to you.
A diagram agent that turns an initial text into a polished explanatory visual, hand-crafted as SVG. It scopes the single claim the diagram must make, proposes 2-3 ASCII wireframe compositions built from proven archetypes, and expands the chosen one using a written design system so results stay consistent across runs. The user decides composition; the design system decides style. Finished diagrams accumulate in a library the agent consults on later runs.
A marketing post agent that puts the headline first. Each post starts from a chosen angle, then a headline workshop generates candidates from proven persuasion formulas (Cialdini, Kahneman, Caples), scores them, red-teams the best, and lets the user pick or rewrite. The body follows in two layers: a System 1 hook to stop the scroll, then System 2 proof to close the deal. The user controls every content decision. Product knowledge accumulates in a shared products/ folder so repeat runs stop re-asking.
gcontext splits everything into two main categories: connections and modules. Connections are the agent's access to external services, while modules are the knowledge and playbooks the agent accumulates over time.
Who the agent is and what it does. Every connected runtime receives this text at the start of every session.
One folder per service. A YAML file declares the secret names and dependencies. A markdown file explains the API in practice. The agent reads the docs and writes the script.
Knowledge the agent accumulates. One topic per folder. Playbooks and logs fill in over time.
Secret values live here, gitignored. The agent sees the names but never the values. Values are injected at run time and scrubbed from every output.
Three commands. The server starts and prints an MCP URL.
Once per client, works from any directory. Any MCP client works.
Claude Desktop: add the server URL to your claude_desktop_config.json manually.
With the MCP connected, run the built-in setup prompt. Describe what you need in plain words. The agent proposes connections and modules, builds them, and verifies each one.
Replace my_instance with the name of your gcontext instance.
A connection gives your agent access to one external service. Each connection is a folder with a YAML manifest for secret names, a markdown file with practical API notes, and a scripts folder for proven procedures.
Learn more →An agent is a module you install into your gcontext instance. It gives the instance a repeatable process: steps to follow, playbooks to consult, and logs to learn from. Each run leaves a trace, and the agent gets better over time.
Learn more →