# Verbatim Connection Setup

Verbatim can work with several AI connection modes. The important distinction is whether the AI can inspect the current project directly, or whether the user exports context into the chat.

## Quick Decision Table

| Use Mode | Communication Type | Can Read Local Project/System? | How Context Gets In | How Changes Get Back | Best Use |
|---|---|---:|---|---|---|
| Local AI | Two-way local communication | Yes | Reads local files/project context directly, depending on configured access and model workflow. | Sends manifests, process outputs, or structured actions back through the local system. | Best when the user has capable hardware and wants local-first file-aware AI. |
| GPT Agent Bridge | Two-way bridged communication | Yes | ChatGPT can inspect current project files through a bridge such as ngrok or another local tunnel. | Sends structured changes/manifests back through the bridge into Verbatim. | Best cloud-AI option when current file inspection matters. |
| Chrome Extension | One-way assisted capture | No | User exports selected project context, code, summaries, lists, boundaries, and the system contract into browser chat. | Captures AI suggestions from browser chat; user reviews, edits, scraps, or sends accepted items to Verbatim. | Best for using almost any browser AI while keeping human review before the system sees changes. |
| Manual Manifest Paste | Manual one-way transfer | No | User manually pastes context, code, contracts, and/or manifests into chat or system intake. | Pasted manifests trigger manual mode and route through the recorder like any structured change. | Best for maximum control, minimum setup, and deterministic handoff. |
| Chat Inquiry to Local AI | Two-way local communication | Yes | User asks local AI to inspect, process, summarize, diagnose, or prepare structured actions from local context. | Local AI can return plans, manifests, diagnostics, or process outputs into the local workflow. | Best for conversational local orchestration. |

## Capability Difference

| Capability | Local AI | GPT Agent Bridge | Chrome Extension | Manual Manifest Paste |
|---|---:|---:|---:|---:|
| Can inspect current files directly | Yes | Yes | No | No |
| Avoids stale or pasted-only context | Yes | Yes | Partial | Partial |
| Requires user to provide/export context | Optional | Optional | Yes | Yes |
| Can work from prepared project context packs | Yes | Yes | Yes | Yes |
| Can send structured changes to recorder | Yes | Yes | Yes | Yes |
| Supports review before execution | Yes | Yes | Yes | Yes |
| Lowest setup friction | No | No | Medium | Yes |
| Best for any browser AI | No | Mostly ChatGPT | Yes | Yes |

## The Mental Model

All modes can help move structured project context into AI workflows, including file code, project overview, dynamic lists, mapping boundaries, intent notes, and the system communication contract.

The key difference is access.

Local AI and GPT Agent Bridge are two-way workflows. They can inspect local project context directly and return structured changes.

Chrome Extension and Manual Manifest Paste are controlled handoff workflows. They cannot read the system themselves, so the user chooses what context goes into the chat, reviews what comes back, and only then sends structured changes to Verbatim.

## Copy Tools That Support Setup

The Pause / quote button opens the Copy Context menu. These options help users prepare the right amount of context for the AI connection mode they are using.

| Copy Option | Use |
|---|---|
| Copy Recording Contract | Gives AI the system communication rules before writing. |
| Copy Project Tree | Shows the project folder/file structure. |
| Copy Project Overview + Intent | Shares project summary, notes, and intent-marked lists. |
| Copy Selection | Shares the currently highlighted item, run, log cluster, code block, or project field. |
| Copy Last Run | Shares what just happened, grouped by the recent timestamp cluster. |
| Copy Recent History | Shares a short view of what the system has been doing recently. |

## Recommended Starting Path

For a first Verbatim tour, Manual Manifest Paste or the Chrome Extension is usually easiest because the user controls every handoff.

For a file-aware workflow, use Local AI or GPT Agent Bridge so the AI can inspect the project directly instead of relying only on exported context.

For browser AI tools that do not have direct file access, use the Chrome Extension or manual copy tools to provide project context intentionally.
