cocosearch-quickstart

CocoSearch Quick Start

Get a project indexed and searchable in under 2 minutes. This skill checks prerequisites, indexes the codebase, and verifies everything works.

Step 1: Check Infrastructure

Before indexing, verify the required services are running. The checks depend on which embedding provider is configured.

First, determine the provider: Check cocosearch.yaml for embedding.provider (or the COCOSEARCH_EMBEDDING_PROVIDER env var). If neither is set, the default is ollama. Also check for embedding.baseUrl (or COCOSEARCH_EMBEDDING_BASE_URL).

All providers need PostgreSQL:

1. PostgreSQL (pgvector):

   docker ps --filter "name=postgres" --format "{{.Names}} {{.Status}}"
   

   • If not running: docker compose up -d (from the CocoSearch project root)

Then check the embedding provider:

2a. If provider is ollama (default):

curl -s http://localhost:11434/api/tags | head -c 200

• If not running: docker compose --profile ollama up -d or ollama serve
• If running but no model: ollama pull nomic-embed-text
• If baseUrl is set, check that URL instead of localhost:11434

2b. If provider is openai or openrouter:

• Without baseUrl: Verify COCOSEARCH_EMBEDDING_API_KEY is set:

  echo ${COCOSEARCH_EMBEDDING_API_KEY:+"API key is set"}
  

  If not set: export COCOSEARCH_EMBEDDING_API_KEY=sk-... No Ollama needed.
• With baseUrl: Verify the custom endpoint is reachable:

  curl -s <baseUrl>/v1/models | head -c 200
  

  API key is not required (local OpenAI-compatible servers typically don't need one).

If PostgreSQL + provider checks pass: Proceed to Step 2.

If nothing is running and user has CocoSearch cloned (Ollama provider):

cd /path/to/cocosearch && docker compose --profile ollama up -d

This starts both PostgreSQL and Ollama in one command.

Step 2: Index the Project

Resolve index name (use the resolved name for all operations):

• Try cocosearch.yaml for indexName field -- if found, use it
• If no config file, call list_indexes() and match the current project's directory name against available indexes. The MCP tools auto-derive index names from directory paths (e.g., my-project/ -> my_project), so a match is likely if the repo was indexed without a config file.
• If no match found, the project is genuinely not indexed -- proceed to create one below. Do NOT abandon CocoSearch tools just because cocosearch.yaml is missing.