Files

There is no provider-neutral files API in v0.11.0. Codex and Gemini expose provider-specific file subpaths; inspect the compile-checked narrow imports.

This client mirrors and verifies upstream-compatible behavior. Upstream runtimes remain the canonical protocol owners.

Referenced examples

Verified example · TypeScript

Narrow imports

examples/narrow-imports.ts

@cavi-ai/api-clientv0.11.048adfa6b

import { ClaudeApiClient } from "@cavi-ai/api-client/providers/claude/messages";
import { CodexFilesClient } from "@cavi-ai/api-client/providers/codex/files";
import { GeminiFilesClient } from "@cavi-ai/api-client/providers/gemini/files";
import { HERMES_PROVIDER_MODULE } from "@cavi-ai/api-client/providers/hermes/runtime";
import { OPENCLAW_PROVIDER_MODULE } from "@cavi-ai/api-client/providers/openclaw/runtime";
import type { TeamManifest } from "@cavi-ai/api-client/contracts";

export function readManifestVersion(manifest: TeamManifest) {
  return manifest.version;
}

export const narrowImports = {
  ClaudeApiClient,
  CodexFilesClient,
  GeminiFilesClient,
  HERMES_PROVIDER_MODULE,
  OPENCLAW_PROVIDER_MODULE,
};

Package imports

Referenced by

Artifact provenance

Package: @cavi-ai/api-client@0.11.0
Release: v0.11.0
Commit: 48adfa6ba7c3d5e8ffee0a6cf2572574ca630fa0
Source: examples/narrow-imports.ts
Tarball SHA-256: 3379cd47b4890d0e00f5949583f90a83367705878b16141e825f66ef5d8819e5
Content SHA-256: 306450f08c69a6e068f80490b1f2cc4f0808af0911fdec5b9b145e33a9ba5534