Skip to content
TCAFTask-Contract AI Development Framework
TCAF 0.3.3

Cline

Use the verified Cline manual-envelope workflow with explicit inspection, single-file write and validation phases.

Content: completeWorkflow: verified with limitations

TCAF 0.3.3 supports Cline through the verified manual-envelope workflow. Native runner-to-Cline invocation is planned separately and must not be presented as available.

Select Cline

python install.py --adapter cline

Or override one run:

tcaf task --target <project> --request "<task>" --adapter cline

Run the command outside Cline. Start a new Cline task, paste the generated Run Envelope unchanged and append exactly one transport marker.

Exact transport markers

TCAF CLINE STEP: INSPECT
TCAF CLINE STEP: WRITE <repository-relative-path>
TCAF CLINE STEP: VALIDATE
  • INSPECT is read-only and authorizes project listing, search and pertinent file inspection.
  • WRITE <repository-relative-path> authorizes at most one write operation to the named file and one write confirmation in that Cline task.
  • VALIDATE is read-only and is used to review current files and developer-reported checks.

The marker may narrow the Run Envelope. It cannot expand target, scope, permissions or output.

One task for each write

Use a fresh Cline task for every authorized file write. After the write:

  1. review the actual file;
  2. confirm whether the intended change occurred;
  3. stop before authorizing the next file;
  4. open a new Cline task with a new WRITE marker when another file is approved.

Do not treat one marker as permission to edit a directory or the entire workspace.

Review gate

Cline should inspect the project and present the Task Contract before consequential edits. The developer approves, corrects or rejects the contract and can narrow the proposed write surface.

If the developer edits files manually, Cline must read the current content before continuing.

Tool limitations

Cline’s UI, approval flow or command execution can occasionally prevent an otherwise valid workflow from continuing automatically.

TCAF does not use terminal commands through Cline by default. The agent should normally report one to three exact DEVELOPER_RUN commands or manual checks.

If Cline remains Pending after an approved write but the file changed, treat the write as performed, review the file and do not approve or repeat it. If the file did not change, start a fresh Cline task for the same bounded step without broadening the request.

A manual verification accepted by the developer can be valid evidence when the task requires UI or environment-specific behaviour.

Verified scope

The manual-envelope path has been exercised with project work and explicit developer approvals. Its status remains verified-with-limitations because host behaviour and permissions can vary.

Native automatic invocation of Cline from the TCAF runner remains planned and is documented separately.