Connect your existing agent
Use Redgold tools from your existing agent and repository. You can add one service at a time while keeping your model provider and delivery workflow. Search, browsers, memory, agent pods and builders have separate permissions; installing a client does not enable every service.
Choose a connection
| Connection | Best for | What it adds |
|---|---|---|
| Setup prompt | An existing agent that can inspect and install local tools | redgold, rac, rci and reusable skills |
| Hosted MCP | An MCP client using remote API tools | API discovery and calls, data and reviewed pipelines; no local binaries |
| Terminal installation | Installing the tools yourself | The same binaries, with explicit platform and update instructions |
The RAC command guide covers the current commands and the access each workflow needs. These connections also work alongside the hosted website.
Ask your agent to set up the tools
Copy the current setup prompt from the splash page into your agent. It points to the reviewed setup skill. The agent documentation index links the related guides and skills. The prompt contains no credentials.
Before running it, make an existing account API key available through your
secret manager as REDGOLD_API_KEY. If you need an account, start with
account access, then create a key in
Settings → API Keys. Keep its value
out of the conversation and repository. Search and browser operations need
their respective service permissions and Billing credit; model API access
alone does not establish either.
The setup skill asks the agent to inspect the installer, install the tools, preserve existing instructions and model settings, and report versions and remaining access requirements. Search verification starts with a quote that executes no provider work. An actual search needs an authorized tier price; remote builds need the project's provisioned endpoint and credentials.
Keep the skills available across sessions
The installer supplies the binaries. Install the reusable instructions into the skill directory your agent uses. Inspect the inventory first:
rac skills list --scope all --json
rac skills show redgold
For Codex user skills:
rac skills install redgold --target "$HOME/.agents/skills"
rac skills install rac-research --target "$HOME/.agents/skills"
rac skills install rac-build --target "$HOME/.agents/skills"
For Claude Code personal skills:
rac skills install redgold --target "$HOME/.claude/skills"
rac skills install rac-research --target "$HOME/.claude/skills"
rac skills install rac-build --target "$HOME/.claude/skills"
Honor an existing custom skill directory. Repository-scoped skills can use
.agents/skills or .claude/skills. Compare locally edited instructions before
using --overwrite. If your release does not bundle a skill yet, the setup
skill links to its public Markdown. Reconnect or start a new agent session if
the new skills do not appear.
Connect through MCP
Add a Streamable HTTP server at
https://api.redgold.ai/api/mcp, authenticated with your account API key.
The MCP reference has Claude Code and Codex configuration,
workspace selection and the complete tool list.
Begin with api_search, then api_describe on a returned operation identifier.
Discovery performs no build, purchase or data write. api_call forwards an
authorized request to that declared operation. Data tools have their own
prepare, quote, run and status workflow.
MCP exposes remote API operations. Local checkout uploads, interactive
terminals and filesystem commands still need their native client, such as
rac cargo or rac pnpm. API discovery does not provision a builder or agent
pod. The MCP connection also leaves your existing model provider settings in
place; using Redgold as a model provider
is a separate option.
Add the service your task needs
| Service | Workflow | Required access |
|---|---|---|
| Agent search | Quote a Quick, Standard or Deep search, then execute within the authorized price | Web-search permission and Billing credit, or a centrally funded grant |
| Managed browser | Quote a hosted session, choose routing, interact and retain results | Browser-session permission and a spending cap; residential routing and CAPTCHA assistance depend on the configured service |
| Memory and conversation search | Discover enabled memory backends, save durable facts and recover earlier decisions | An authenticated, configured memory backend or accessible conversation index |
| Managed agent compute | Work in persistent Kubernetes workspaces and inspect assigned sessions | A provisioned environment and corresponding agent permissions |
| Remote CI, builds and tests | Submit finite Cargo or pnpm work and retrieve outputs | The project's approved builder endpoint, credentials and budget |
The command guide includes quotes, replay rules and examples. For managed pods, continue with coding agents and agent operations. A persistent workspace preserves files; it does not keep every terminal process running through a restart.
Check and maintain the connection
Record rac version --json, redgold --version and rci --version, the skill
locations, and the result for each service you configured. A working MCP
discovery request or installer download does not verify search, persistence or
build execution. Report an unavailable service as remaining setup.
To update, inspect and rerun the official installer using the existing key, then compare and reinstall the selected skills. See installation troubleshooting for platform requirements and common access errors. The documentation's public index and full Markdown are also available to agents.