BUILT IN · INTERACTIVE PROGRAMS
Terminal Tick
For programs with a screen and keyboard interaction, such as htop or a Python REPL. The Agent reads the current screen and can send input.
MEET TICK
A shared language
for programs
and agents.
A Tick is something an Agent can work with: a connected program, a command, or an artifact. The Agent can read its content, use its available operations, and receive new information.
WORKING TOGETHER
Describe · Read
Call · Update
Extension Ticks use the Tick Protocol to describe capabilities, expose state, accept calls, and report changes. Three request methods and one update notification.
tick/describeDescribe capabilities- What the Tick is and which Tick Tools it provides.
tick/readRead state- Read the current state, such as the Counter’s value.
tick/callCall a tool- Call a Tick Tool, such as increment to increase the count.
tick/updateReport a change- The program reports new state for a subscription to deliver to the Agent.
These are extension Tick protocol messages. The Agent uses TickDescribe for capabilities, TickRead for state, TickCall for declared tools, and TickManage for lifecycle and subscriptions. TickUpdate is an event. Package Skills explain launch commands and login prerequisites; they do not replace a live capability catalog.
SHARED VOCABULARY
From one instance
to ongoing work.
The interface, tools, and specification use these names for the same concepts.
- Tick Instance
- One independent run or artifact. A program can have multiple instances, each with its own identity and state.
- Tick Tool
- A callable capability declared by an Extension Tick, such as the Counter’s increment tool.
- Tick Update
- New information from an instance: a state change, a command exit, or an artifact feedback request.
- Tick Subscription
- An explicit relationship delivering an instance’s updates to a Loop at its delivery frequency.
- Loop
- Holds a goal and its progress. It can execute, wait, and continue when new information arrives.
- View
- An interface presenting an instance. Multiple Views can attach to one instance; closing a View does not end it.
FOUR TYPES OF TICK
Three built-in types.
One way to extend.
Terminal, Shell, and Artifact Ticks are built in. Extension Ticks connect programs through the Tick protocol, exposing their own state, tools, and updates.
BUILT IN · COMMAND TASKS
Shell Tick
For running a command, such as cargo build or a report script. The Agent reads its output and is notified when it exits. Long commands can also run in the background.
BUILT IN · CONTENT
Artifact Tick
A Doc or Page that people and agents can edit. Requests made with @tickloop in comments go to the associated Agent, one by one.
EXTENSION · PROGRAM INTEGRATION
Extension Tick
A program implements the Tick protocol to expose structured state, callable tools, and updates. Market data, monitoring, and custom tools can connect this way. The bundled example Ticks use it too.
Terminal and Shell Ticks differ in how they run and interact, not how long they run. A Terminal Tick provides screen and keyboard interaction; a Shell Tick runs a command and exposes its output.
CONTINUING THE WORK
New information.
A reason to continue.
Tick Updates supply new information. A Loop holds the goal and its progress. While waiting with no work to handle, the Agent makes no model calls.
- Tick Subscription · Delivery paceOpening or reading an Extension or Terminal Tick does not subscribe. Subscriptions deliver changed state every 1, 10, or 30 minutes, with 1 minute as the default.
- Tick Update · State and requestsFrequent state changes merge into the latest snapshot; query history when needed. Shell completion arrives immediately, and @tickloop feedback requests are delivered individually.
- View · Separate from the instanceClosing a Tick’s view does not end it. Multiple views can attach to the same instance while the Agent continues using it for the original goal.
FOR DEVELOPERS
Connect new capabilities.
Implement the Tick protocol to expose a program’s structured state, tools, and updates. Message formats, integration rules, and complete examples live in the specification.
Read the Tick protocol specification →