TICKLOOP · AI AGENT

An agent that stayswith your work.

Connect your tools through Ticks. Write code, collaborate on documents and slides, choose your model, and delegate work to subagents.

Install Watch how it works

Tickloop · Launch Ready10:00

tickloop · ~/tickloop/launch

Artifacts

↗Event notes

Ticks

↻◉Event schedule

◉ Monitor 2

⏵⏵ Auto · Claude Opus 5 · Context 8%

tickloop.ai · Run of show · Demo

↗ Event notes · Artifact

Follow the event schedule.

00:00 / 00:24

Concept demos · Imagined Ticks, sample data, and simulated execution. Time is compressed.

.scenario-list, #scenario-panel { display: none; }Enable JavaScript to play the five workflows, or explore installation and the Tick protocol. Install · Tick

The tools to do the work

Plan tasks, read and write code, run commands, and delegate to subagents. Add Skills for specialized workflows and turn an idea into a result you can inspect.

Keep the goal in progress

A Loop holds the goal and its progress. Schedules, Tick updates, and new instructions let the Agent continue from that state. When there is no work to handle, it waits quietly.

Keep improving the result

Work together on Docs, Pages, and Slides. People and agents can edit the same artifact. Comment with @tickloop on a linked artifact to request the next step.

HOW IT WORKS

One goal. Room to continue.

A Loop holds your goal and its progress. Your instructions, a schedule, Tick updates, or a message from a subagent can move it forward.

TimeContinue on a schedule
ProgramsNew state, completed commands
AgentResults from subagents
YouMessages and @tickloop feedback

1 · update →TickA program exposes its state and reports what changes.
2 · deliver →Tick SubscriptionDeliver the latest state at your chosen interval. No change, no model call for that subscription.
3 · continue →LoopKeep the goal and its progress, ready for the next step.
4 · actAgentUnderstand the change, act within your permissions, and record the result.

Subscription intervals: 1 · 10 · 30 minutes Your permission rules apply Read and call Ticks on demand, too

THE TICK PROTOCOL

Programs become
an agent’s eyes and hands.

The Tick protocol uses line-delimited JSON-RPC 2.0. Three request methods and one update notification expose state and tools, in any language.

describe
Describe the program and its tools.
read
Read the current state.
call
Call a declared tool.
update
Report a change for subscriptions to deliver.

→ {"jsonrpc":"2.0","id":1,"method":"tick/call","params":{"tool":"mark","args":{"price":384.6},"revision":"1"}}
← {"jsonrpc":"2.0","method":"tick/update","params":{"seq":43,"data":{…}}}

Built-in adapters also connect existing shell commands and interactive terminal programs. Explore the protocol →

A WORKFLOW

From a goal to a result.

10:00
Set the goal
Describe the outcome, the source material, and the boundaries.
10:05
Connect the programs
The Agent reads the Ticks it needs and subscribes when you ask it to follow changes.
10:10
Continue when things change
A Tick delivers new information. The Agent continues from the existing goal.
10:12
Prepare the result
Delegate independent work when useful, then create documents, pages, or slides you can inspect.
10:14
Keep improving it
Comment with @tickloop on a linked artifact to request the next change.

MODELS

Choose the model for the work.

Choose your model and connection in /provider. Use API keys or, where supported, sign in with a provider account.

Anthropic
OpenAI
Google
xAI
GitHub Copilot
DeepSeek
Kimi
Zhipu GLM
MiniMax
Alibaba Bailian

PERMISSIONS

Your rules. At every step.

Separate access from actionReading files, changing content, running commands, and accessing external services follow their applicable permission rules.
Permissions come firstOperations pass through permission checks. You decide when confirmation is needed; Auto stays within the same scope.
Uncertain results stay visibleIf a change times out or loses its connection after dispatch, it is not automatically resent.
Know where work happensIn the current version, the Agent and local Ticks run on your computer. Model requests go to your chosen provider; artifacts live in the separate Artifacts service.

Install

Get started with Tickloop.

Install, connect a model, and begin.

$ brew install tickloopai/tap/tickloop

Or use the native installer:

$ curl -fsSL https://tickloop.ai/install.sh | sh

$ cargo install --locked tickloop

Cargo downloads and verifies the complete official program during installation. Ready to run when installation finishes; application source remains private.

Developer builds from private source

Requires current stable Rust and a source checkout. Run from the repository root:

cargo install --locked --path agent/tickloop --bin tickloop
cargo install --locked --path tickhost/host --bin tickhost
cargo install --locked --path tick/reader --bin tick-reader

# Start the Agent, then connect a model in /provider
$ tickloop
# Update your installation
$ tickloop update

Current releases support macOS. Native, Homebrew, and Cargo launcher installations can update in the background and include the short command tl. Add Herdr to view Ticks side by side.

QUESTIONS

Before you begin.

Do I need to code?

Describe your goal in plain language. Installation and model setup need basic terminal familiarity. The Agent can help write custom programs when you need them.

What work can I use it for?

Develop and test code, organize research, analyze data, and create documents, pages, and presentations. Use a linked artifact’s @tickloop comments to request follow-up work.

Which programs can I connect?

Programs that implement the Tick protocol expose structured state and tools. Other interactive programs, such as log viewers and REPLs, can open as Terminal Ticks for the Agent to read and interact with.

Does my computer need to stay on?

The current version needs your computer to stay on. Closing the view leaves the Agent running, but it cannot work while your computer sleeps. After a shutdown or process exit, reopen and continue the task.