opencode

Connect OpenCode to Chroma

Give an AI agent your Chroma instance as a tool and it can manage the vector store itself instead of asking you to. It can create a collection, add records, read and count what is stored, fork a collection for a safe experiment, and delete records that no longer belong, calling each operation as a tool while it works a task. Wire it into a hosted coding agent in NoClick and it can build and maintain a retrieval index end to end.

Loading preview…
Opens a workflow with 36 tools ready to use.

Tools OpenCode gets

Pick the operations you want and each becomes a tool the agent can call directly while it works.

Chroma

36 tools
Query (Vector)

Similarity search by a query embedding vector.

Search (Text)

Full-text / semantic search using query text — Chroma embeds it server-side via an attached function.

Add Records

Add records to a collection (fails if IDs already exist; use Upsert for insert-or-update).

Upsert Records

Upsert records — inserts new IDs and updates existing ones (idempotent sync).

Update Records

Update existing records by ID (fails if an ID does not exist; use Upsert otherwise).

Get Records

Get records by ID or filter.

Count Records

Count the number of records in a collection.

Delete Records

Delete records by ID, metadata filter, or document content filter.

Upload & Index Document

Upload a document file, chunk + embed it, and add the records.

List Collections

List collections in the tenant/database.

Get Collection

Get a collection's metadata and configuration by name.

Create Collection

Create a collection.

Update Collection

Rename a collection or replace its metadata.

Delete Collection

Permanently delete a collection and all its records.

Count Collections

Count the total number of collections in the database.

Indexing Status

Get the indexing status of a collection (records indexed vs pending).

Fork Collection

Fork (copy) an existing collection into a new one.

Fork Count

Get the number of times a collection has been forked.

Get Collection by ID

Get a collection's metadata by its UUID.

Get Collection by CRN

Get a collection by its Cloud Resource Name (CRN).

Attach Function

Attach an embedding or processing function to a collection.

Get Attached Function

Get details about a function attached to a collection.

Add Function Input

Add input data to an attached function (e.g. provide documents to embed).

Detach Function

Detach (remove) a function from a collection.

Get Tenant

Get metadata about a tenant.

Create Tenant

Create a new tenant.

Update Tenant

Update a tenant's configuration.

List Databases

List all databases in the tenant.

Create Database

Create a new database in the tenant.

Get Database

Get metadata about a database.

Delete Database

Delete a database and ALL its collections. DESTRUCTIVE.

Healthcheck

Check whether the Chroma server is healthy.

Heartbeat

Get the server heartbeat (nanosecond timestamp).

Get Version

Get the Chroma server version string.

Reset Server

Reset the Chroma server. DESTRUCTIVE — wipes ALL data across all tenants and databases.

Get User Identity

Get the identity of the currently authenticated user.

What you can build

When a new document lands in your pipeline, embed it and add the records to the right Chroma collection automatically.
On a schedule, count the records in each collection and post the totals to your team so you can watch the index grow.
When a source record is deleted upstream, delete the matching records from Chroma so search never returns stale hits.
Stand up a fresh database and collection for each new project, then attach an embedding function so records are ready to store.
Fork a production collection before a risky reindex, run the changes against the copy, and leave the original untouched.
Look up a collection by ID or CRN, pull its records, and feed them into an AI step for evaluation or cleanup.

About OpenCode

OpenCode is an open, model-agnostic command-line coding agent. In NoClick it runs hosted and gains your apps as tools, so it can act on real systems rather than just edit files. Wire an integration into the agent and OpenCode can use that app’s operations directly while it works. It is a flexible choice when you want an open agent with broad model support and real tool access.

Open and model-agnostic
Flexible across many underlying models
Good general-purpose tool use
Lightweight to point at a focused task

Frequently asked questions

Build a custom OpenCode agentChroma integration

Open your OpenCode agent in one click

NoClick runs OpenCode for you with Chroma wired in as tools. Connect your account and run.