Cohere Continuous Integration

Overview

Make the required CI path deterministic and secret-free while preserving a trusted lane that detects real SDK and API drift.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Required pull-request checks should mock the application provider port and make no Cohere network calls.
• Fork pull requests must never receive Cohere secrets.
• A trusted branch, schedule, or manual workflow may run one bounded live probe with explicit spend and timeout limits.
• Pin runtime, SDK, action, and lockfile versions so failures are reproducible.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Identify required checks, fork behavior, secret scopes, and the existing provider adapter.
2. Add offline request-mapping, response, stream, error, retry, and redaction fixtures.
3. Make the offline lane required and assert that no network fallback is possible.
4. Add a separate protected live job with concurrency control, one request, timeout, and model discovery.
5. Upload sanitized test metadata without prompts, credentials, or customer content.
6. Document who may trigger the live lane and how model/API drift is triaged.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Error Handling

Cohere Error Diagnosis

Overview

Classify the failing layer before changing code, and return a minimal reproduction plus the safest next action.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• 400 and 422 usually indicate an invalid request contract or incompatible feature combination.
• 401 means the key is absent, invalid, expired, or injected into the wrong runtime.
• 402 indicates a billing limit; 429 indicates a current endpoint or model limit.
• Eligible 5xx and transport failures may be retried boundedly; deterministic client errors must not be retried.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Capture timestamp, endpoint, status, SDK version, resolved model, redacted request shape, and provider request identifier when available.
2. Check Cohere status and determine whether failures are global, model-specific, environment-specific, or request-specific.
3. Compare required v2 fields and feature combinations with the current reference.
4. Run one minimal non-sensitive reproduction with retries disabled.
5. Apply the smallest correction or mitigation and verify with one bounded probe.
6. Record the classification, evidence, correction, and rollback or escalation owner.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved docume…

Cohere Retrieval-Augmented Generation

Overview

Create a measurable retrieval pipeline that separates indexing, query embedding, candidate retrieval, reranking, generation, and citation checks.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Embed indexed passages with input_type=search_document and user queries with input_type=search_query.
• Keep the embedding model, output type, dimensions, normalization, and document schema in index metadata.
• Use Rerank v4 on a bounded candidate set before generation and retain document IDs.
• Pass selected documents to Chat v2 and validate returned citations against those IDs.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Define document IDs, chunking rules, metadata filters, and an evaluation query set.
2. Resolve and pin a live Embed model, then index documents with the document input type.
3. Embed each query with the query input type and retrieve a bounded candidate set.
4. Rerank candidates with a live v4 model and record scores and selected IDs.
5. Generate from only the selected evidence with citation options appropriate to the use case.
6. Evaluate retrieval recall, rerank quality, answer faithfulness, citation validity, latency, and cost before release.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer …

Cohere Tool-Using Agent Loop

Overview

Let the model propose typed tool calls while application code validates, authorizes, executes, correlates, and limits every side effect.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Define each v2 tool as a function with JSON Schema parameters.
• Read proposed calls from the response message and correlate results with tool_call_id.
• Append the assistant tool-call message and tool results to the application-managed messages history.
• Command A+ was the current high-capability tool-use candidate on the review date; resolve availability before pinning it.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Define a minimal tool allowlist, strict schemas, timeouts, and side-effect classifications.
2. Resolve a live tool-capable model and submit the user message plus tool definitions.
3. Validate tool name, arguments, tenant scope, and approval state before dispatch.
4. Execute read-only calls automatically only if policy allows; pause for consequential writes.
5. Append correlated tool results and continue until content is returned or the iteration budget is exhausted.
6. Test unknown tools, invalid arguments, duplicate calls, timeouts, denial, and loop exhaustion.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer iden…

Cohere Cost and Usage Tuning

Overview

Build a reproducible cost model from live prices and measured workload units, then optimize only within approved quality and safety thresholds.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Do not embed a permanent price table; capture the pricing page date and applicable commercial terms.
• Separate Chat input/output, Embed input, Rerank search, and platform infrastructure costs.
• Newer model access and production capacity can have account-specific terms.
• A cheaper model or smaller context is acceptable only after representative evaluation passes.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Collect current public prices or contracted rates with effective date and currency.
2. Measure per-request input, output, Embed, Rerank, retry, cache, and failure units by workload class.
3. Forecast baseline, expected, and peak volume with capacity and retry assumptions.
4. Evaluate model routing, context reduction, retrieval pruning, batching, caching, and duplicate suppression.
5. Set per-tenant and global budgets, alerts, admission controls, and an owner-approved degradation path.
6. Reconcile forecast with actual billing regularly and investigate material variance.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestric…

Cohere Data Handling and Privacy

Overview

Decide what may cross the provider boundary from the signed agreement and application purpose, then enforce that decision before each request.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Cohere's public privacy policy distinguishes enterprise Customer Data from general personal information and points to enterprise commitments.
• Do not infer retention, residency, training use, deletion, or subprocessors from a generic policy when a contract governs the workload.
• Embeddings and logs can encode sensitive information even when raw text is absent.
• Data minimization and tenant authorization must happen before Chat, Embed, Rerank, or tool calls.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Classify inputs, retrieved documents, outputs, embeddings, logs, and tool data by tenant and jurisdiction.
2. Map each data class to the signed terms, approved region, retention, deletion, access, and incident requirements.
3. Block disallowed classes and minimize, tokenize, or redact approved inputs before the provider call.
4. Apply tenant filters before retrieval and keep document identifiers safe for citation auditing.
5. Configure logs and caches with allowlisted fields, encryption, access control, and deletion tests.
6. Produce a data-flow record and obtain privacy or legal approval for unresolved contractual claims.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaini…

Cohere Support-Ready Debug Bundle

Overview

Produce evidence that support can act on without copying credentials, prompts, customer data, or an unrestricted environment dump.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Collect only allowlisted environment-variable names and redact values.
• Record endpoint, SDK/runtime versions, model ID, status, latency, retry count, and provider request identifier when available.
• Represent request and response structures with synthetic or hashed content.
• Keep the bundle local until a human approves its recipients and data classification.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Create a dedicated output directory with restrictive permissions and a retention deadline.
2. Capture runtime, SDK, lockfile, network path, timestamp, and Cohere status metadata.
3. Serialize a redacted request-shape summary and the smallest synthetic reproduction.
4. Include bounded probe output, application correlation ID, and sanitized stack trace.
5. Scan the bundle for key formats, authorization headers, emails, prompts, and customer identifiers.
6. Return the manifest and checksum for human review; do not transmit it automatically.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Error Handl…

Cohere Deployment Integration

Overview

Release the application around Cohere without embedding the key in clients, turning health checks into billable generation, or hiding provider failure.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Call Cohere from a trusted server runtime; never expose the provider key to browsers or mobile clients.
• Use a local process health check and a separate protected provider-readiness probe.
• Streaming paths require proxy buffering, idle timeout, cancellation, and client-disconnect tests.
• Model selection and fallback must be explicit deployment configuration reviewed against current availability.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inspect the target platform's secret, egress, timeout, streaming, autoscaling, and rollback behavior.
2. Inject CO_API_KEY from the platform secret manager and restrict access to the service identity.
3. Set explicit model IDs, request bounds, client timeouts, concurrency, and circuit-breaker thresholds.
4. Deploy to a non-production environment and test cancellation, throttling, timeout, and provider outage behavior.
5. Canary production traffic while watching quality, error, latency, queue, and spend signals.
6. Promote or roll back using recorded thresholds and preserve the deployment evidence.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorizatio…

Cohere Enterprise Access Control

Overview

Use Cohere's documented Team roles for platform administration while enforcing fine-grained workload authorization in the application and secret manager.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Cohere Teams document Owner and User roles; Owners have additional membership, production-key, billing, and production-form powers.
• Team users can still have broad key and usage capabilities, so provider roles alone are not application RBAC.
• Separate human administration from runtime service identities and environment-specific credentials.
• Enforce tenant, model, endpoint, tool, and budget policy before provider calls.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inventory Cohere teams, members, roles, keys, environments, service identities, and billing owners.
2. Map Owner and User capabilities to least-privilege job functions and separation-of-duties requirements.
3. Move runtime keys into approved secret stores and bind retrieval to named workloads.
4. Implement application authorization for tenant data, allowed models, endpoints, tools, and spend.
5. Review membership, keys, usage, invoices, and access evidence on a fixed cadence.
6. Test member removal, key rotation, service revocation, tenant denial, and emergency access.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, …

Cohere Bounded First Request

Overview

Prove one selected endpoint end to end while keeping model choice, input type, output bounds, and evidence explicit.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Discover a live model for the intended endpoint before pinning it.
• Chat v2 accepts a messages array and returns content under the response message.
• Embed v2 requires input_type and embedding_types; use search_document for indexed passages and search_query for queries.
• Rerank v2 orders supplied documents; select rerank-v4.0-pro for quality or rerank-v4.0-fast for measured latency needs.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Confirm authentication with cohere-install-auth and choose exactly one endpoint.
2. Resolve a live model from the catalog or Models API and record the resolved ID.
3. Use a non-sensitive, tiny fixture and set explicit output or result bounds.
4. Issue one v2 request and capture status, latency, model, billed-unit metadata when available, and response shape.
5. Validate non-empty Chat content, expected embedding dimensions, or monotonic Rerank ordering.
6. Return the minimal reproducible request with credentials redacted.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved docu…

Cohere Incident Runbook

Overview

Restore a safe user experience first, preserve evidence, and distinguish provider incidents from local regressions before making changes.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Check Cohere's status page, but treat service-specific evidence as authoritative for your workload.
• Separate authentication, billing, throttling, model retirement, provider 5xx, retrieval, and application failures.
• Use only pre-approved degradation paths such as queueing, cached answers, read-only mode, or an evaluated model route.
• Never debug by dumping keys, prompts, documents, or unrestricted environment variables.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Open the incident record and capture start time, impact, environment, endpoint, model, release, and correlation IDs.
2. Check provider status and compare control traffic, regions, models, and recent local changes.
3. Classify the failure and apply the smallest reversible mitigation within the incident authority matrix.
4. Protect data and side effects while monitoring recovery against explicit thresholds.
5. Escalate to Cohere with the redacted debug bundle when provider assistance is required.
6. After recovery, verify normal quality and capacity, document timeline and cause, and assign preventive work.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys,…

Cohere Installation and Authentication

Overview

Select the current v2 client for the repository, keep credentials outside source control, and prove access with a read-only Models API request.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• TypeScript uses CohereClientV2; Python uses cohere.ClientV2.
• Use CO_API_KEY as the local injection contract or pass an approved secret reference explicitly.
• Pin a compatible SDK range and commit the resolved lockfile; do not copy an unbounded install command into CI.
• Verify authentication by listing accessible models rather than generating billable output.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inspect manifests, lockfiles, existing provider adapters, and secret-loading conventions.
2. Choose TypeScript, Python, or REST and pin the current compatible SDK major.
3. Document CO_API_KEY without writing its value, then update ignore rules if local environment files are used.
4. Initialize the v2 client with the injected key and an explicit timeout.
5. Run one read-only model-list probe and record the SDK version, status, and model count only.
6. Assign ownership for key creation, rotation, revocation, and environment separation.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer ide…

Cohere Local Development Loop

Overview

Keep normal development offline and deterministic while preserving one tightly bounded path that proves the real v2 contract.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Mock the application-owned provider interface, not generated SDK internals.
• Store representative v2 Chat, Embed, Rerank, stream, error, and tool-call fixtures with secrets removed.
• Gate real calls behind an explicit environment switch and a protected evaluation key.
• Treat model IDs and SDK response types as external contracts covered by adapter tests.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Locate the provider boundary and existing test framework before adding files.
2. Define a narrow Cohere port for the operations the application actually needs.
3. Add sanitized fixtures for success, rate limit, timeout, and malformed response paths.
4. Write offline contract tests for request mapping, response parsing, and redaction.
5. Add one opt-in live smoke test with a single request and hard timeout.
6. Document the exact offline and live commands and ensure the default test command makes no network call.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Error Handling

Cohere Provider Migration

Overview

Treat provider migration as a semantic and operational change, not a search-and-replace of SDK calls.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Cohere offers native v2 SDKs and an OpenAI compatibility API, but the compatibility surface omits Cohere-specific features.
• Chat messages, tool schemas, citations, safety controls, usage fields, errors, and stream events require explicit mapping.
• Embedding model changes require a parallel index because vectors from different contracts are not interchangeable.
• Model identifiers, limits, prices, and availability must be resolved for the target environment.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inventory provider calls, prompts, tools, embeddings, indexes, streaming, errors, budgets, and user-visible quality.
2. Define a provider-neutral application port and golden evaluation set before implementing the target adapter.
3. Map supported semantics and record every incompatibility, especially citations, tools, safety, and structured output.
4. Build a parallel target embedding index with versioned model and dimension metadata.
5. Shadow or canary representative traffic and compare quality, latency, errors, throttling, and cost.
6. Cut over gradually, retain rollback through the observation window, and retire old keys and indexes only after approval.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, an…

Cohere Multi-Environment Configuration

Overview

Keep credentials and capacity isolated while promoting one versioned provider contract through increasingly production-like environments.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Use separate keys or provider deployments per environment and never fall back from production to an evaluation key.
• Resolve model availability per environment because Cohere platform and cloud-provider IDs differ.
• Promote configuration references, not secret values.
• Keep evaluation fixtures synthetic or approved and align staging limits closely enough to expose production failure modes.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inventory environments, accounts, teams, cloud platforms, keys, owners, and data classes.
2. Define a validated configuration schema for provider, base URL, model IDs, timeouts, retries, and budgets.
3. Store secrets in environment-specific managers and bind access to runtime identities.
4. Run the same offline contracts everywhere and a bounded provider probe only in trusted environments.
5. Promote resolved configuration through review with quality, capacity, and rollback evidence.
6. Continuously detect key reuse, model drift, missing budgets, and unauthorized configuration changes.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents,…

Cohere Observability

Overview

Expose enough evidence to separate application, retrieval, model, capacity, and provider failures without logging credentials or customer content.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Measure queue, retrieval, provider, first-event, completion, and tool durations separately.
• Label metrics with bounded dimensions such as endpoint, operation, resolved model, environment, outcome, and retry class.
• Keep prompts, documents, embeddings, keys, and raw tool arguments out of telemetry by default.
• Pair operational metrics with sampled quality, citation, and safety evaluations.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Define service objectives and an allowlist of telemetry fields before instrumenting.
2. Create counters for requests, outcomes, retries, throttles, circuit transitions, and tool decisions.
3. Create histograms for queue, retrieval, provider, first-event, completion, and end-to-end duration.
4. Record usage and cost units without tenant names or unbounded request IDs as metric labels.
5. Build alerts for availability, sustained throttling, queue age, latency, quality, and spend.
6. Test redaction, trace propagation, stream cancellation, and incident correlation.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers,…

Cohere Performance Tuning

Overview

Tune from workload-specific measurements and representative quality thresholds rather than copying universal latency numbers or synthetic benchmark claims.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Resolve models and their current context and output limits from the live catalog.
• Measure Chat time to first event and completion separately from application queue and retrieval time.
• Batch Embed inputs within documented request constraints and track inputs per minute.
• Choose Rerank v4 pro or fast from measured relevance and latency on representative queries.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Define a representative workload, quality floor, latency objective, concurrency, and cost ceiling.
2. Instrument queue, retrieval, provider, first-event, completion, and post-processing durations.
3. Establish a cold and warm baseline with fixed inputs and resolved model IDs.
4. Test one variable at a time: model, context size, output bound, stream mode, Embed batch size, Rerank candidate count, or cache.
5. Reject changes that improve speed while violating quality, citation, safety, or cost thresholds.
6. Record the selected configuration, confidence interval, capacity headroom, and rollback trigger.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embedd…

Cohere Production Readiness

Overview

Convert a staged Cohere integration into a reversible production release with explicit owners, thresholds, and evidence.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Public-facing workloads require the appropriate production key and acceptance of Cohere's current terms.
• Sensitive-use declarations can affect approval and capacity; verify the actual organization state.
• Models, limits, pricing, and deprecations must be checked at release time.
• Production readiness includes retrieval or task quality, not merely a successful API call.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Verify production key ownership, model availability, contractual data terms, and current capacity.
2. Attach offline and bounded live evaluations for quality, citations, safety, and failure handling.
3. Confirm secret isolation, tenant boundaries, redaction, timeouts, retries, and circuit breaking.
4. Set latency, error, throttle, cost, quality, and queue thresholds with named responders.
5. Run a staged canary with rollback criteria and no unapproved model fallback.
6. Record GO or NO-GO, approvers, evidence links, release window, and rollback command owner.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.

Cohere Rate-Limit Control

Overview

Treat limits as a live per-key, endpoint, and model contract rather than a single permanent requests-per-minute number.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• The reviewed page lists Chat limits per model; several newer variants require contacting sales for production capacity.
• On the review date, Embed was expressed in inputs per minute, while Rerank was expressed in requests per minute.
• Trial usage includes a monthly cap, and production arrangements can vary.
• A successful load plan must measure actual account behavior and preserve headroom instead of copying a static table.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Identify key type, endpoint, resolved model, request batch size, and documented current limit.
2. Convert limits into request, input, and token budgets as applicable.
3. Apply a shared queue with bounded concurrency, jittered backoff, and a total retry deadline.
4. Honor provider retry guidance when present and stop retrying deterministic client errors.
5. Load test below the approved ceiling with non-sensitive fixtures and record saturation behavior.
6. Alert on sustained throttling, queue age, dropped work, and budget exhaustion.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted …

Cohere Reference Architecture

Overview

Define clear boundaries between clients, policy, retrieval, provider access, tools, evaluation, and operations so model behavior cannot bypass application controls.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Keep a typed Cohere provider adapter behind an application service boundary.
• Apply tenant authorization and metadata filters before retrieval, then preserve document IDs through Rerank and citations.
• Dispatch tools through a policy-enforcing registry with schemas, approvals, timeouts, and audit evidence.
• Resolve model, lifecycle, capacity, and platform IDs through environment configuration and current provider sources.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Capture users, tenants, data classes, quality objectives, latency targets, side effects, and failure tolerance.
2. Draw trust boundaries for clients, API, policy, retrieval, vector store, Cohere, tools, logs, and secret stores.
3. Define request, result, citation, tool, error, and telemetry contracts at each boundary.
4. Choose synchronous, streaming, queued, or degraded paths with bounded retries and cancellation.
5. Attach offline evaluation, protected live probes, canarying, observability, budget, and incident controls.
6. Review threats, data terms, capacity, model lifecycle, rollback, and named ownership before implementation.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, own…

Cohere SDK Integration Patterns

Overview

Wrap generated SDK clients behind a small application contract so model changes, provider errors, and migrations stay localized.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Instantiate one configured v2 client per runtime process unless tenancy requires a separate credential boundary.
• Require callers to supply an operation purpose, bounded timeout, and resolved model ID.
• Retry only transient transport, 429, and eligible 5xx failures with jitter and a total-attempt ceiling.
• Normalize Chat content, citations, tool calls, Embed vectors, Rerank scores, usage, and provider request metadata at the boundary.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inventory current direct SDK calls and group them by Chat, Embed, Rerank, and model discovery.
2. Define typed request and result contracts that expose only application-required fields.
3. Centralize timeout, redaction, retry eligibility, and model resolution.
4. Implement streaming as an async iterator with cancellation and terminal-event validation.
5. Add contract fixtures for success, partial stream, timeout, limit, and schema drift.
6. Migrate one call site at a time and delete direct SDK access only after parity tests pass.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, …

Cohere Security Baseline

Overview

Protect the credential and the data path around the model; safety modes complement but do not replace application security controls.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Keep keys in an approved secret manager, separate them by environment, and rotate on exposure.
• Authorize retrieval and tool execution in application code before any data leaves its trust boundary.
• Cohere safety modes are model- and feature-dependent; tools or documents can constrain the available mode.
• Treat model output, citations, tool arguments, and retrieved text as untrusted data.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Map data classes, tenants, endpoints, tools, logs, and credential owners.
2. Enforce server-side key injection, outbound host allowlisting, timeouts, and request-size limits.
3. Apply tenant filters before retrieval and authorize every tool call independently of model intent.
4. Choose and test the supported safety mode for each resolved model and feature combination.
5. Redact logs and validate output before rendering, persistence, or side effects.
6. Test key exposure, prompt injection, cross-tenant retrieval, unsafe output, and tool escalation.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environ…

Cohere API and SDK Upgrade

Overview

Inventory legacy behavior, move through the documented v2 contract, and prove semantic parity before removing rollback paths.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• V2 uses messages instead of separate message, preamble, and managed conversation history fields.
• V2 requires explicit models; Embed also requires embedding types.
• V2 tools use JSON Schema and correlate results with tool-call IDs.
• Legacy Generate, Summarize, Classify, managed connectors, selected models, and fine-tuning paths appear on Cohere's deprecation schedule.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Inventory SDK versions, endpoints, parameters, models, stream events, connectors, fine-tunes, and response parsing.
2. Read the current migration and deprecation pages and classify each dependency as live, legacy, deprecated, or shut down.
3. Add golden contract tests around current user-visible behavior and failure paths.
4. Introduce the v2 client and provider adapter while retaining a feature-flagged rollback path.
5. Migrate request and response shapes, then reindex embeddings if their model contract changes.
6. Canary representative traffic, compare quality and operations, and remove v1 only after rollback criteria remain clear.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, …

Cohere Streaming and Application Events

Overview

Separate response-stream events from durable business events and replace deprecated managed connectors with application-owned v2 tools.

Prerequisites

• The target repository, runtime, environment, and accountable owner
• An approved Cohere team and key for any live verification
• Current quality, security, privacy, capacity, and change-control requirements

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.

Current Contract

• Chat v2 streaming is a server-sent response stream, not an inbound signed webhook surface.
• Handle typed content, citation, tool-call, and terminal events and tolerate additive unknown event types.
• Managed v1 connectors are deprecated; v2 retrieval and web search use user-defined tools.
• If the application emits durable callbacks, define its own authentication, signing, idempotency key, retries, and dead-letter policy.

Authentication

Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.

Instructions

1. Choose response streaming, tool streaming, or an application-owned durable event; do not conflate them.
2. Implement an async iterator with cancellation, timeout, terminal-state validation, and unknown-event telemetry.
3. Buffer partial content only within explicit memory and latency bounds.
4. Correlate tool calls and results before continuing the v2 message loop.
5. For durable internal events, persist state before delivery and enforce signature and replay-window validation.
6. Test disconnects, duplicate delivery, out-of-order events, partial streams, unknown types, and terminal errors.

Approval Boundaries

Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.

Output

Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization head…