Deterministic Tessie vehicle reads, confirmed controls and health checks through protected dynamic vehicle policy and the existing OneCLI gateway.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
A NanoClaw overlay plugin that reads and controls Tesla vehicles through the Tessie REST API. Everything the agent does is a deterministic script: the model picks the script and words the result, it does not drive the API call by call.
This is the Tesla1 foundation (issue #1): the Tessie client, vehicle allowlist, chat authorization, cached reads, confirmed controls, a no-wake health check, packaging and CI. Calendar charging (#2) adds a protected standing-owner workflow and reusable measured-energy estimates; enrollment and native acceptance remain separate. The read-only vehicle morning summary (#4) integrates with the optional Admin gather source; generic firmware-active coverage and native acceptance remain open. Tesla3/5/6 remain separate work. Running-late (#7) adds the event-bound consumer and protected host companion; source publication still requires installed authority and actual native acceptance. Solar and Powerwall (#8) stays deferred.
Merged source is not an installed plugin and a passing test suite is not a live smoke test; see docs/setup.md for the owner steps that remain.
result: true is reported as accepted; only matching cached state at or after actual host dispatch produces confirmed. Failed readback preserves accepted receipts.| Skill | Purpose |
|---|---|
tessie-ops | Action router: list vehicles, inspect the allowlist, read state, read location, preview and run controls, confirm state, tag drives |
tessie-charge | Native next-day charge planning, private status and reusable measured departure estimates; cadence remains unenrolled |
tessie-running-late | Event-specific approval, native three-minute polling and a shared two-message limit across owner and approved recipient |
tessie-brief | Read-only deterministic vehicle lines for morning gather; explicit unknown coverage, no vehicle wake or controls |
tessie-watch | Daily precheck that wakes the agent only for a low unplugged battery, a credential or API failure, or unreadable state |
| Rule | Purpose |
|---|---|
rules/vehicle-brief-policy.md | Fixed cached vehicle evidence, literal brief lines and explicit unknown coverage |
rules/calendar-charge-policy.md | Native standing owner enrollment, retained baseline/uncertainty and one evening notice |
rules/running-late-approval.md | Native per-event delegation, fixed host transport and the shared delivery budget |
rules/tessie-credentials.md | The token lives in the vault; the agent never holds, requests or prints it |
rules/vehicle-allowlist.md | Current vehicle access follows the protected dynamic or explicit host predicate |
rules/provider-identity.md | Provider namespace and declared surfaces remain consistent |
rules/location-privacy.md | Precise location stays in owner chats |
rules/command-authorization.md | Controls need an authorized chat, a named plan and a reported outcome |
rules/nanoclaw-skill-root.md | Command blocks use the container's skill root |
Install the published provider with tessl install jbaruch/nanoclaw-tesla.
The overlay loads per chat through containerConfig.additionalTiles with the bare name nanoclaw-tesla, on a protected owner-authorized chat, including the existing owner main chat. Token, allowlist, install and verification steps are in docs/setup.md; the supported commands and their limits are in docs/command-surface.md.
python3 -m venv .venv && . .venv/bin/activate
python -m pip install --require-hashes -r requirements-dev.lock
python -m pre_commit install
python -m ruff check tests skills && python -m ruff format --check tests skills
python -m pyright
python -m pytestThe normal commit hook runs pinned Gitleaks source through pre-commit 4.7.0. Keep the hook installed; Renovate’s enabled pre-commit manager in renovate.json renews its source SHA.
Tests use synthetic VINs, a frozen clock and a fake transport; nothing reaches Tessie. requirements-dev.lock is compiled from requirements-dev.txt with uv pip compile requirements-dev.txt --python-version 3.11 --generate-hashes -o requirements-dev.lock.
The owner enrolls this repository in the existing central review GitHub App. Publication uses the repository TESSL_TOKEN secret; never create a broad review token or store CI credentials in .env.
The development jbaruch/coding-policy dependency pins 0.5.10. This new provider
is outside the host contract’s enumerated floating-manifest set. No committed
scanner tracks the Tessl registry; the maintainer checks it monthly with
tessl update jbaruch/coding-policy --yes and lands any reviewed manifest update
as a separate change. Renovate is this repository's only
dependency scanner, running in full mode before 6am on Monday. Its native
pip requirements
and GitHub Actions
managers renew Python dependencies, external action and reusable workflow digests,
and the exact CI Python patch within 3.11; the enabled pre-commit manager renews hook pins.
Minor, patch and digest updates share one PR; major updates require Dependency
Dashboard approval. Renovate uses chore(deps) commits and opens at most five PRs
at once. After a Python dependency bump, regenerate requirements-dev.lock with
the command above and run the checks in .github/workflows/test.yml.