Build context like you build code

$ curl -LsSf gcontext.ai/gcontext/install.sh | sh

GitHub

Works withClaude CodeCursorCodexpi.dev

See it in action

Context modules give your agent structured files it can navigate by itself.

Your context is just files

No vector database. No prompt templates. A file tree your agent reads top-down.

context/

├─ llms.txt # the index the agent reads first

├─ integrations/

│ └─ postgres/

│ ├─ info.md

│ └─ module.yaml

├─ workflows/

│ └─ deploy/

│ ├─ info.md

│ └─ module.yaml

└─ tasks/

└─ sprint/

├─ info.md

└─ module.yaml

See it work

Hover or tap a panel to take a closer look.

[ Compare ]

What happens without structure

No context vs. structured modules, side by side.

no contextno memory

Chat 1

Investigate support ticket SUP-123

I don't have access to that ticket. What system is it tracked in? What's the issue?

It's in Linear. User hasn't received payment, probably Supabase. Here are the logs: [14:31:02] ERR payment.webhook timeout [14:31:03] ERR edge_fn: payment-process

Based on those logs, the webhook timed out. Likely a Supabase edge function failure. Check payment-process errors around 14:31.

new chat

Chat 2

What's the status of SUP-123?

I don't have context for that ticket.

no contextno memory

Chat 1

Investigate support ticket SUP-123

I don't have access to that ticket. What system is it tracked in? What's the issue?

It's in Linear. User hasn't received payment, probably Supabase. Here are the logs: [14:31:02] ERR payment.webhook timeout [14:31:03] ERR edge_fn: payment-process

Based on those logs, the webhook timed out. Likely a Supabase edge function failure. Check payment-process errors around 14:31.

new chat

Chat 2

What's the status of SUP-123?

I don't have context for that ticket.

with contextcontext aware

Chat 1

Investigate support ticket SUP-123

Fetching Linear · SUP-123

Querying Supabase · payment_logs

Pulling Datadog · traces

Root cause: Supabase edge_fn timed out at 500ms. Webhook never fired. Applying fix...

Updating Supabase · edge_fn timeout → 2s

Closing Linear · SUP-123 → Done

Done. Timeout bumped to 2s and deployed. Ticket closed.

new chat

Chat 2

What's the status of SUP-123?

Checking Linear · SUP-123

Resolved. Agent closed it at 15:45 UTC. Status: Done. Fix: edge function timeout bumped to 2s.

[ Build ]

context/

company.md

integrations/

stripe.md

linear.md

Describe your stack, gcontext structures it

Hover to view →

[ Execute ]

readgenrun

Context in, code out

Hover to view →

No context vs. structured modules, side by side.

no contextno memory

Chat 1

Investigate support ticket SUP-123

I don't have access to that ticket. What system is it tracked in? What's the issue?

It's in Linear. User hasn't received payment, probably Supabase. Here are the logs: [14:31:02] ERR payment.webhook timeout [14:31:03] ERR edge_fn: payment-process

Based on those logs, the webhook timed out. Likely a Supabase edge function failure. Check payment-process errors around 14:31.

new chat

Chat 2

What's the status of SUP-123?

I don't have context for that ticket.

no contextno memory

Chat 1

Investigate support ticket SUP-123

I don't have access to that ticket. What system is it tracked in? What's the issue?

It's in Linear. User hasn't received payment, probably Supabase. Here are the logs: [14:31:02] ERR payment.webhook timeout [14:31:03] ERR edge_fn: payment-process

Based on those logs, the webhook timed out. Likely a Supabase edge function failure. Check payment-process errors around 14:31.

new chat

Chat 2

What's the status of SUP-123?

I don't have context for that ticket.

with contextcontext aware

Chat 1

Investigate support ticket SUP-123

Fetching Linear · SUP-123

Querying Supabase · payment_logs

Pulling Datadog · traces

Root cause: Supabase edge_fn timed out at 500ms. Webhook never fired. Applying fix...

Updating Supabase · edge_fn timeout → 2s

Closing Linear · SUP-123 → Done

Done. Timeout bumped to 2s and deployed. Ticket closed.

new chat

Chat 2

What's the status of SUP-123?

Checking Linear · SUP-123

Resolved. Agent closed it at 15:45 UTC. Status: Done. Fix: edge function timeout bumped to 2s.

Used by

maatapp.com

soundmurai.com Bleak AI

bleakai.com

“It has transformed how I approach solving support tasks. From a boring task I was always procrastinating into something actually fun to do.”

Stefano Saitta·CTO, MAAT·

“Our gcontext Cloud agent helps us build posts for insights.soundmurai.com. It pulls global live-music data from our database to generate the insights.”

Eduard Aymerich·Co-Founder, Soundmurai·

Your workspace, your rules

Open source and local. Your context lives in your repo as files — portable, yours to keep.

CLI

Open source

Build and sync context modules from your terminal. Free forever.

$ curl -LsSf gcontext.ai/gcontext/install.sh | sh

View on GitHub →

gcontext Cloud

Coming soon

Everything in the CLI, plus a visual editor, AI chat with your context, and managed infrastructure.