ai-hats-cline
A Cline surface plugin for the ai-hats
framework. It registers the cline CLI as a first-class
ai-hats provider through the ai_hats.providers entry point, so ai-hats
discovers it with zero edits to src/ai_hats/** (the T10 IoC seam, HATS-870).
Install it alongside ai-hats and cline appears next to the built-ins:
$ ai-hats list providers
agy → GEMINI.md
claude → (session cache)
cline → (session cache)
(The right-hand column is where the role reaches the surface from. Only agy has a project-root file; claude and cline receive the composition from the per-session cache and write nothing to the root.)
Then compose any role onto cline:
$ ai-hats -p cline -r <role> # HITL: launches an interactive cline TUI
What it owns
ClineProvider— theai_hats.providers.Provideradapter forcline:- the composed role reaches cline inline via
-s "<role>"(no staticCLINE.md—update_system_promptis a no-op); - HITL launches the interactive TUI (
cline -i); the automate path runs headless (cline --yolo --json "<prompt>"); --worktreeis never passed (ai-hats-wt owns isolation);- the role's skills are materialized into the per-session cache
(
<cache_root>/sessions/<sid>/skills— outside the project, default~/.cache/ai-hats/<project-key>/, HATS-1398) and delivered to cline via--config <cache>(cline scans<base>/skills) — nothing lands in the project root (clean-root invariant, HATS-1171).CLINE_DATA_DIRis pinned to the real cline home so--configkeeps the machine's auth.
- the composed role reaches cline inline via
ClineParser+resolve_transcript— cline's~/.cline/data/sessions/<id>/<id>.messages.jsonis discovered by the provider and parsed into a realaudit.md(👤/👾 turn markers) andusage.json(token metrics), soreflectgets a factual layer for cline sessions (HATS-960, HATS-1087).
Requirements
clinev3.x onPATH, authenticated (cline auth).ai-hats(this plugin depends on the integrator for theProviderABC, per ADR-0014).
Not yet here
- Runtime bash-tool hooks: cline's TS plugin sandbox needs
jiti(unbundled), so ai-hats ships no plugin — guarding falls toSurfaceGuard. A nativehooks.jsonguard (no jiti) is tracked in HATS-1083. - cline
teams/spawn, and PyPI publish.
Release files for ai-hats-cline 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ai_hats_cline-0.5.0.tar.gz | 18.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_hats_cline-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.5 kB
Release files / ai_hats_cline-0.5.0.tar.gz
| Download URL | ai_hats_cline-0.5.0.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4fb5e98cb8e282c0de6b1259bcf1fa19ee1949fcae26bbf84add2fc93ce94df8
|
|
BLAKE2b-256 checksum How to use checksums |
df65a668eecbc52934bbe73bd25800e049a0a3f4ed1e3e41a9a23330f6c16484
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.
Transparency logRelease files / ai_hats_cline-0.5.0-py3-none-any.whl
| Download URL | ai_hats_cline-0.5.0-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd459af2124084cc53d4164c2592482181b2fe0984ed4ffdf23c00f488438c1b
|
|
BLAKE2b-256 checksum How to use checksums |
32306b939bb0e79cfc549a9657abd13eff35c1f379a1d732b14fd4ea66e15456
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.
Transparency log