Skip to content
TCAFTask-Contract AI Development Framework
TCAF 0.4.0 · public preview

Select an adapter

Choose the TCAF transport that matches the actual host without changing scope, authority or core behavior.

An adapter defines how a TCAF Run Envelope reaches an AI host. It changes transport, not task scope or developer authority.

Selection

Automatic selection uses host information, TCAF_ADAPTER, environment detection and finally the registry default. You can record a preference during installation:

python install.py --adapter codex

Or override one operation:

tcaf task --target <project-path> --request <bounded-request> --adapter cline

Codex

  • Adapter ID: codex
  • Transport: native
  • Status: verified

Codex can access and edit the target directly within the permissions and edit surface declared by the run.

The five main project operations are:

tcaf bootstrap
tcaf adopt
tcaf plan
tcaf task
tcaf sync

tcaf run is available for direct registered-agent invocation, but normal usage should prefer the named operation that describes the work.

Native access does not authorize unrelated edits, bypassing review gates or automatic Git operations.

Cline

  • Adapter ID: cline
  • Transport: manual-envelope
  • Status: verified-with-limitations

The bounded manual-envelope procedure is verified. Native runner-to-Cline invocation is not currently a verified path.

Use the generated envelope in a new Cline task and append one documented transport marker:

TCAF CLINE STEP: INSPECT
TCAF CLINE STEP: WRITE <repository-relative-path>
TCAF CLINE STEP: VALIDATE

The marker may narrow the envelope. It may not expand target, scope, permissions or output.

Generic CLI

  • Adapter ID: generic-cli
  • Transport: stdout
  • Status: framework-aligned

This adapter prints the Run Envelope for another command-line host. Transport alone does not grant direct file-writing capability.

Generic chat

  • Adapter ID: generic-chat
  • Transport: host-resource
  • Status: framework-aligned

Use generic chat only when the host can provide the required persistent framework resources and exact target evidence. Previous chat memory alone is not reliable TCAF project state.

The rule that never changes

Every adapter must preserve one target, the approved edit surface, developer review gates, preservation-first behavior, explicit evidence reporting and separation from commit/push operations.

A more capable host can execute more of the approved work. It does not receive wider authority.

See Validation coverage for current verified boundaries.