If Jev only chooses, who actually does the work?

Tocket never writes app code or drives tools itself; Cursor, Claude, CI, or similar workers execute the recorded choice while Tocket keeps shared memory across sessions without lock-in.

What stops an agent from running a risky tool anyway?

The decide step records allow, block, or ask in JSON and the work step refuses blocked or ask-gated applies without an explicit force flag, keeping the gate in files rather than middleware.

Do I have to adopt the CLI or can I use files alone?

No. The protocol is plain markdown plus JSON you can create by hand; the CLI only automates scaffolding, defaults, and checks around the same files.

How do I try it without polluting my main branch?

Create a test branch, scaffold there, commit the notebook files, run sessions, then eject the scaffold or delete the branch; the developer guide documents the safe-testing flow.

What does Tocket install and require?

npx @pedrocivita/tocket init scaffolds a .context/ directory, TOCKET.md, and the matching agent file, detecting your stack and executor. It is MIT-licensed and adds no runtime dependencies. TYPESAFE_API_KEY is optional: without it, decide stays on the heuristic stub.

What does the tool gate actually enforce?

tocket decide --choice tool_gate:allow,block,ask records the gate before risky tools, and tocket work --apply refuses to proceed on block or ask with exit code 2 unless --force is passed. Shadow and log-only applies also need --force.

How do I remove Tocket if I do not want it?

Run npx @pedrocivita/tocket eject with confirmation, which removes all Tocket files, or just delete the test branch you created. Tocket writes plain markdown files committed to git, so nothing hides in a store you cannot inspect.

CommunityJev Integrations & Adapters

Tocket

File-first project notebook where many agents share context in .context/ files while Jev only judges the next step and records it as JSON.

See highlights

Open github.com

Stars: 38
Language: TypeScript
License: MIT
Published by: Community
Author: pedrocivita
Last verified: Oct 2026

pedrocivita/tocket

User repository on GitHub

View on GitHub

Tocket Transmition Protocol

Forks: 2
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

Tocket is the project notebook: folders/files many AI agents read and write together. It is not a chat and does not do the work alone. Jev (and similar) only picks among options and saves that choice in the notebook. Cursor/Claude/GrokBot/CI still do the work. Agents work · Tocket remembers · Jev only chooses the next step.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import

Works forJev for Classification Jev for Routing

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Adds versioned markdown state, architecture, and progress files plus JSON decisions any file-reading agent can resume without lock-in.
Records the next move with a decide command and a tool gate, then a work command plans or applies a receipt while honoring blocks.
Scores handoff chunks and loads conditional gotcha packs so workers read filtered context instead of the whole notebook.
Scaffolds with one init command, checks health with doctor, and runs stubbed without a key until a live judging key is exported.

Watch out

A file convention, not a chatbot, browser driver, or code generator; workers still do the work. Try on a branch first; eject removes the scaffold. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

chat2jev

A Next.js workbench that converts OpenAI-compatible Chat Completions requests into Jev state and typed questions, compares chat output against structured judgments, and publishes saved question packs as proxy routes. The interface is mainly in Chinese.