Automations

Scheduled commands in Thirdfy Console. Monitor, suggest, or execute within limits you approve.

Automations are scheduled commands that run under your delegation. They use the same validation as Command and appear in the Automations tab.

Create automations in Command by describing what you want on a schedule. Command checks the prompt, asks you to confirm limits, then saves the schedule. Pause and resume from the Automations tab.

Console automations vs EarnClaw agents

	Console automation	EarnClaw hosted agent
Where it runs	Thirdfy scheduled execution	EarnClaw always-on hosted runtime
Best for	Test and refine a strategy with history and spending limits	Full-time agents with templates, schedules, and a dashboard
How you start	Natural language in Command	EarnClaw deploy wizard today

Use Console automations to prove a strategy works before you move it to a hosted agent.

Coming soon in Console

You will be able to deploy EarnClaw agents and create agent templates from Console without leaving the operator surface. The intended flow:

Design and run an automation in Command.
Review execution history in Activity and Automations.
Turn proven logic into an EarnClaw template when you are ready for always-on hosting.

Until that ships, deploy full agents on EarnClaw. Thirdfy still validates execution the same way on both paths.

Automation types

Every automation gets one of three types. The type controls whether writes can run on their own.

Type	What it does	Typical schedule
Read-only monitor	Checks balances, positions, yield, or alerts. No swaps or transfers.	Every few hours or once per day
Rebalance suggestion	Compares options and suggests moves. You still confirm before execution.	Every few hours
Bounded execute	May execute writes within a USD cap you approved at creation.	Daily buy, capped rebalance

Examples Command understands:

"Every 6 hours, check my Base USDC yield options and alert me if APY drops by more than 50 bps." → read-only monitor
"Every morning at 9 UTC, review my Base wallet and alert me if idle USDC is above $500." → read-only monitor
"Every 4 hours, if delegated Base USDC is above $1,000, look for safe yield options. Cap any rebalance at $250." → rebalance suggestion
"Buy $10 worth of ETH every day at 9 AM." → bounded execute with a $10 cap

Some prompts are rejected at creation if they imply uncapped recurring swaps without explicit limits. Ask Command to add a dollar cap or a confirmation step.

Schedules

Automations support:

Repeating interval: every N hours (for example every 4 or 6 hours)
Daily at a set time: fixed UTC time (for example 9:00 UTC each day)

Minimum interval and daily run limits apply per account.

Requirements

Before an automation can run writes:

Delegation must be active for the wallet Command uses.
Signing must be ready (embedded wallet or external wallet setup complete).
Execution balance or free requests must cover each run (same billing as Command).

Read-only monitors can often start with lighter setup. Types that execute writes need delegation and explicit confirmation at creation.