2.04K
total weekly downloads
42 packages
agenthttp
Reserved. Nothing here yet.
@agenthttp/core
Reserved. Nothing here yet.
portrail
Remote-control Codex and Claude Code over a local HTTP gateway.
rayspec
The unscoped `rayspec` launcher — a thin bin that hands control to the RaySpec CLI (`@rayspec/cli`). Installing `rayspec` (or `npx rayspec`) puts the `rayspec` command on PATH: `rayspec init` scaffolds a starter project, `rayspec doctor`/`plan` validate a
@rayspec/adapter-anthropic
The Anthropic Claude Agent SDK adapter (the abstraction's stress case). Maps the neutral `Backend` interface onto `@anthropic-ai/claude-agent-sdk` (pinned), so the same declared agent runs unchanged on any RaySpec backend adapter.
@rayspec/adapter-codex
The OpenAI **Codex** adapter — the fourth backend, with full parity to the openai/anthropic/pi adapters. Maps the neutral `Backend` interface onto `@openai/codex-sdk` (pinned).
@rayspec/adapter-deepgram
The Deepgram speech-to-text provider adapter. Implements the provider-neutral STT port (`@rayspec/stt-port`: `SttAdapter` contract, transcript types, registry, media-resolver, normalizer) against the Deepgram API.
@rayspec/adapter-openai
The OpenAI Agents SDK adapter — the **reference adapter**. Maps the neutral `Backend` interface onto `@openai/agents` (pinned, zero caret), so the same declared agent runs unchanged on any RaySpec backend adapter.
@rayspec/adapter-openai-tts
The OpenAI text-to-speech adapter behind the provider-neutral [`@rayspec/tts-port`](https://github.com/rayspec-labs/rayspec/tree/main/packages/kernel/tts-port) contract: one REST call to `/v1/audio/speech`, no provider SDK, the credential resolved lazily
@rayspec/adapter-pi
The Pi adapter. Runs the same neutral `AgentSpec` as the reference adapter onto the same neutral surface — central `dispatchTool`, real `ConvTurn`/`ConvPart` types, and a real per-step journal.
@rayspec/agent-runtime
The workflow **agent node**: runs an agent step inside a durable workflow, resolving the configured backend adapter and handler registry, with fakes provided for deterministic tests.
@rayspec/api-auth
The first HTTP server composition: the Hono `OpenAPIHono` app factory plus the `@rayspec/auth-core` services it composes. The public surface is the app factory and those auth services.
@rayspec/audio-runtime
The product-neutral Tier B **Audio/Media session capability**. It owns audio session/track upload, idempotent resumable chunk ingest, finalize, media storage, playback-token minting, and range/streaming playback — with **zero product vocabulary**. It is t
@rayspec/auth-core
HTTP-free authentication and authorization primitives: API-key HMAC, authorization checks, audit logging, and auth configuration. Unit-testable without a server; composed into the HTTP surface by `@rayspec/api-auth`.
@rayspec/bundle
The one reader and writer of RaySpec application bundles (`.ray`). The CLI reads and writes bundles through it, and a hosting service imports the same package, so every consumer accepts and refuses exactly the same archives. The format itself — the manife
@rayspec/bundle-closure
What goes into an application bundle (`.ray`), decided from the spec without running anything. `rayspec pack` builds on it: this package computes the explicit inclusion list, the preview and the manifest fields, and [`@rayspec/bundle`](../bundle) writes t
@rayspec/bundle-contract
The **bundle contract** in code: the format of a RaySpec application bundle (`.ray`), of the encrypted migration snapshot and of the managed hosting receipt. It carries the JSON Schemas and vocabularies of the contract, their TypeScript types, the canonic
@rayspec/capability-bridges
The durable-workflow ↔ capability composition seams for the four ingress capabilities (audio · conversation · file · record), merged into one package. Each capability's canonical event → WorkflowInputEvent adapter + the fail-closed *Sink a deployment inje
@rayspec/cli
The RaySpec CLI — a READ-ONLY diagnostic floor (`rayspec doctor` static parseSpec, `rayspec plan` read-only deploy front-half, `rayspec gen-handler`, the passive `rayspec bundle inspect`/`verify` of a .ray bundle, and `rayspec pack`, which writes a .ray b
@rayspec/conversation-runtime
The generic Tier-B conversational-ingress capability (conversation_input) — an idempotent client-keyed conversation create plus a bounded JSON turn submit that persists the user turn in a capability-owned ledger and emits a durable workflow trigger. Produ
@rayspec/core
Kernel primitives shared by every RaySpec runtime and adapter: the **neutral `Backend` interface** that all agent-backend adapters implement, plus foundational building blocks such as bounded request bodies, the error-class hierarchy, and content hashing.
@rayspec/db
The tenant-scoped data layer. Request-path and run-core code only ever hold a **`TenantDb`** (obtained via `forTenant`) — the raw, unscoped database handle stays at the composition root. Postgres-backed, with tenant isolation as a construction-time guaran
@rayspec/durable-dbos
The DBOS adapter for the neutral DurableExecutor. The ONLY package that imports @dbos-inc/dbos-sdk — @rayspec/platform / run-core / the adapters stay DBOS-free (engine asymmetry lives inside this adapter). Runs the EXISTING runAgent off-request inside one
@rayspec/file-runtime
The generic Tier-B file-ingest capability (file_input) — a bounded raw-byte upload plus a JSON submit that seals the file and emits a durable workflow trigger. Product-neutral; a record×audio hybrid (record_input donates the manifest/event/submit template
@rayspec/foundation
The reviewed workflow foundation: core workflow types, the capability registry, idempotency primitives, and an in-memory executor. `@rayspec/workflow-durable` wires this foundation onto the real platform primitives for durable execution.