Skip to main content

ContextGo Documentation

ContextGo Docs
Local-First AI Native Workbench

Organize context, workbenches, agents, automation, publication paths, and remote access into one long-running system

ContextGo is not just a chat box and not just one agent runtime. It helps bring your real workflow into the system, keeps the desktop host doing the execution, keeps web and mobile available as remote work surfaces, and lets a working agent grow into a real channel-facing service surface.
Why It Matters

Why it is different from a typical AI tool

ContextGo is not trying to be another stronger chat assistant. Its value comes from combining the layers that real long-running work actually depends on.
No Agent Raising

You do not need to "raise" an agent first

Start from real work, then gradually add runtimes, skills, automation, and publication capability.
See the workflow entry
Context First

Bring the workflow in before asking for intelligence

Files, pages, browser context, project docs, and external sources enter first, so the agent can work on real material.
Open Context
Host + Remote

Let the desktop host keep working while web and mobile stay available

Execution authority stays on the host. Web and mobile stay available as continuous work surfaces.
Open Remote & Devices
Product Spine

Understand ContextGo through its product spine

If you think of ContextGo as a single conversation page, you miss the actual structure. A better model is a multi-layer work system.
Workbench

Work begins in the Workbench

Conversation, browser work, artifacts, and future specialist work surfaces all live under the workbench host.
Open Workbench
Context

Long-term value lives in Context

Context Connector, Context Engine, and Session / Project / Space decide whether the system can really keep understanding your work.
Open Context
Capabilities

Agents, runtimes, packages, and skills assemble capability together

ContextGo separates execution backend from capability bundles so the product can act like a work platform instead of one runtime wrapper.
Open Agents & Capabilities
Publish

A working agent can move into real channels

Channels, audiences, groups, threads, and publication binding let a working agent grow beyond one private local thread.
Open Publish
Use Cases

Enter through real work instead of a feature list

If you do not want to understand the full product structure first, the best path is to start from the scenario that already looks like your real work.
Bring It In

Bring your workflow into ContextGo

Start from existing files, pages, docs, and tasks instead of rebuilding a new system from zero.
Open the use case
Research

Research and browser workflow

Keep browser context, web research, and reusable findings inside one continuous workflow.
Open the use case
Builder

Coding and builder workflow

Combine code runtimes, project context, browser work, file outputs, and automation into one builder system.
Open the use case
Remote

Personal remote workbench

Let the desktop host keep running while web and phone stay available for checking, controlling, and continuing work.
Open the use case

Recommended first path

If you want to start today, do not try to understand every capability at once. This sequence is more reliable.
  • Read What Is ContextGo and Quick Start first so the host, remote, and context model is clear.
  • Then move into Use Cases and choose the entry that matches your real work.
  • Once one real task is working, come back to Context, Publish, and Collaboration for the longer-term system model.