GroundedPair technical beta

GroundedPair is a provider-independent AI pair-programming workbench. Prepare a request with selected repository context, exchange it manually with an AI provider, inspect the response and continue through developer-controlled execution and verification.

This is an early technical beta for Apple Silicon macOS. The source repository is currently private. Use is governed by the included LICENSE.txt beta terms. The beta is free to install and use; your chosen AI service is separate.

Installation

This beta supports Apple Silicon macOS with desktop VS Code 1.141 or newer. Open a local project folder that you trust. Remote workspaces and browser-based VS Code are outside this beta's supported scope.

In VS Code, open Extensions and search for GroundedPair by publisher brianronock. Choose Install Pre-Release Version (or Switch to Pre-Release Version if a release version is already installed). Open a local project folder that you trust. Run GroundedPair: Open Cockpit from the Command Palette.

If you received a VSIX directly for a manual installation, use the Extensions More Actions menu, choose Install from VSIX, and select that file instead.

No separately installed GroundedPair CLI, Node.js, pnpm or provider API key is required. Git is needed for workspace change observations, and Bash is needed for script preparation and execution. Request, Response and Tools are the default workbench in every trusted local project folder.

First task

1. In Request, describe one small task and the desired response.
2. In Tools, preview a Project Tree or use Find Paths to locate relevant files. Use Exact Files to inspect and attach the evidence the task needs.
3. Return to Request, inspect the attachments, then Prepare and Export the request as text or JSON. Review the exact exported content before sharing it.
4. Manually provide that request to your usual AI provider. GroundedPair does not send it for you or authenticate the provider.
5. Read the returned material. Capturing ordinary advice in Response is optional. Capture it when you need GP's response inspection, executable preparation or evidence continuation tools; review it before deciding to use it.
6. If appropriate, prepare executable material and place it in the terminal. GroundedPair does not press Enter. Review the exact command, run it yourself, and inspect the outcome.
7. Record the observed result and verification evidence, then prepare a continuation when more work is needed.

Use a disposable test project for the first execution trial. An AI response is an untrusted proposal; syntax checking does not certify its safety or correctness.

Choose the path that fits the task

Request prepares what you want to send. Tools supplies selected local evidence. Response lets you inspect returned material and, for supported scripts, prepare a developer-controlled terminal step. These are tools to use when needed, not three mandatory steps for every conversation.

Expected response kind expresses what you requested. Actual material kind describes what the provider returned; choosing Script does not turn advice into executable code. Text remains review-only.

Capture is an in-memory snapshot, not a saved conversation or permanent record. For durable notes, save accepted findings in your own project documentation or retain a deliberately exported exchange. An export is a handoff artifact, not a restorable GP session.

Use your existing provider separately: copy or export from GP, send it in that provider's app, website or editor extension, then bring back material only when GP's next-step tools are useful. GroundedPair supplies no provider subscription and requires neither Copilot nor an integrated chat panel.

What the repository tools provide

• Project Tree shows bounded directory structure and file paths, with an adjustable depth. It does not read source content or establish architecture.
• Find Paths searches literal path names. It is not code-content or semantic search. Pass relevant results to Exact Files when you need their contents.
• Exact Files reads explicitly selected files for inspection and attachment. Use it directly when you already know the paths.

Previewing tool results does not attach them automatically. Attached snapshots remain fixed when you continue exploring; refresh and replace an attachment deliberately when you need newer evidence. Inspect the included content before sharing it. An attachment-only request is useful when the existing conversation already explains why the provider needs another file.

Scripts, results and continuation

For Script responses, ask for raw Bash beginning with #!/usr/bin/env bash, or exactly one block labelled bash whose content begins with a shebang. There must be no prose outside that block. The full captured response stays unchanged; executable content is derived and inspected separately. Preparation diagnostics can be included in Continue with Script correction to request a clean answer. Syntax checks do not establish safety, correctness or successful execution.

After you run a script, inspect available terminal output and read-only workspace observations. File changes are not proof that tests passed. Add your own observed result or assessment when useful, then prepare a follow-up request. Recording an outcome is optional; continue with only the evidence the next question needs.

The side drawers provide Session, a newest-first in-memory interaction record, and Reality, which distinguishes path guidance, exact file evidence, workspace observations and developer assessment. Neither is durable session storage or independent proof of an AI claim.

Known limitations and privacy

• Pair sessions are held in memory. Hiding the panel retains it, but closing it or restarting VS Code loses the session. Exported requests are separate files, not restartable sessions.
• Automatic terminal-output capture depends on VS Code shell integration. Use manual output entry and workspace observations when capture is unavailable.
• Script preparation uses /bin/bash. Native Windows execution is not covered.
• Workspace-change observation requires Git. In a non-Git folder the current preview reports a generic safe-operation failure; manual result evidence and continuation still work.
• Prepared requests may contain private source code. The selected evidence, exported files and material transferred to a provider remain the developer's responsibility. The workbench does not establish permission to share them.
• Script preparation creates temporary files outside the repository. Exported requests and temporary scripts are not removed by uninstalling the extension.
• The workbench does not automatically apply changes, execute proposed commands, commit, push or contact an AI provider.

Feedback and removal

Use the Marketplace Q & A for usage questions and feedback. Do not post private source, credentials or confidential logs.

For a beta trial, record the build version, macOS and VS Code versions, the task, the first point of confusion, expected and observed behavior, and whether a second task was easier. Review screenshots and logs for private content before sharing them through an agreed feedback channel. No feedback is sent automatically.

Disable or uninstall GroundedPair from the VS Code Extensions view. Keep or remove your own exports deliberately. Removing the extension does not revert changes or commands you chose to execute in your project.