Samples Structure & Design Choices — .NET
> This file documents the structure and conventions of the .NET samples so that
> agents (AI or human) can maintain them without rediscovering decisions.
## Directory layout
AGENTS.md
Instructions for AI coding agents working in the Python codebase.
**Key Documentation:**
- [DEV_SETUP.md](DEV_SETUP.md) - Development environment setup and available poe tasks
- [CODING_STANDARD.md](CODING_STANDARD.md) - Coding standards, docstring format, and performance
Multimodal user inputs support both legacy (`text`, `binary`) and draft-style (`image`, `audio`, `video`, `document`) shapes.
- Interrupted runs complete with `RUN_FINISHED.outcome.type == "interrupt"` and canonical `outcome.interrupts`; do not document
into the Agent Framework as a context provider. It automatically analyzes file attachments
(documents, images, audio, video) and injects structured results into the LLM context.
## Public API
| Symbol | Type | Description
credentials.
- **`RedisCollection` / `RedisStore`** - Experimental generic vector storage and search over native HASH and JSON
documents. `_vector_store.py` contains settings, connection/codec/schema/filter helpers, the collection, and
the store, separate from the preexisting history/context
Samples Structure & Design Choices — Python
> This file documents the structure and conventions of the Python samples so that
> agents (AI or human) can maintain them without rediscovering decisions.
## Directory layout
asked to rewrite history.
- Keep release pull requests focused on version metadata and release documentation.
- Do not commit local build artifacts such as `dist/`, `build/`, or generated wheel/sdist files.
## Publishing
from '../../core';
import * as cxapi from '../../cx-api';
if (FeatureFlags.of(this).isEnabled(cxapi.MY_NEW_FLAG)) { ... }
```
## Documentation
### JSDoc
- Document all public APIs (classes, methods, properties, interfaces) when first introduced
- Summary line, blank
foo.rs`).
- **Debug symbols in release** (`profile.release.debug = true`).
- **`#![warn(missing_docs)]`** -- public items must be documented.
## ANTI-PATTERNS (THIS PROJECT)
- **Do not use `any` types or type assertions** -- this is Rust
github.com/gofrs/uuid/v5`
- Write unit tests for new functionality. Use table-driven tests when appropriate
- Document exported functions and types
- Keep comments concise, focused on "why" not "what"
- Update documentation when
avoid dashes entirely. The only exception is CLI flags (e.g. `--port`).
## Boolean Environment Variables
Document boolean env vars using only `0` and `1` in CLI help, SKILL.md, docs pages
docs.corsair.dev/llm-gateway.
## Product note
The hosted product moved from `corsairdev/hosted` to `corsairdev/hub`.
`hosted` receives documentation updates only
this repository. Keep changes small, match the current rewrite architecture, and prefer the documented daemon/API boundaries over behavior from the old TypeScript implementation.
## Repo layout
- `backend/` — Go rewrite of Agent
instructions help customers deploy, call, and troubleshoot the Cosmos3
Certified NIM from this public documentation directory.
For guided customer workflows, load
`.agents/skills/cosmos3-nim-user/SKILL.md`.
## Default behavior
- Start by asking whether the customer
driven scenarios and log utilities are in `simulator_tests/` with the `communication_simulator_test.py` harness.
Authoritative documentation and samples live in `docs/`, and runtime diagnostics are rotated in `logs/`.
## Build, Test
maintained model, endpoint, capability, or schema lists unless the
contract requires them. Prefer the documented API/schema and server-side
validation over brittle client-side guesses.
## Preserve SDK contracts and compatibility