Yekar.AI
Login

Put it to work

Run recurring work on the business's clock

Express recurring work once and have it evaluated against the timezone the business uses.

Talk to usRead the docs
Captured from the product Demo workspace
Schedule work in the timezone your team uses, including daylight-saving transitions.

What this changes for your team.

Schedule triggers accept a standard five-field cron expression plus an IANA timezone. The worker evaluates due occurrences on that local clock, so daylight-saving transitions follow the selected timezone rather than a fixed UTC guess.

How it works in practice.

  1. 01

    Choose Schedule and enter or generate a five-field cron expression.

  2. 02

    Select the IANA timezone whose local calendar should govern it.

  3. 03

    Attach published agents and review each firing in trigger history.

What you can plan around.

The behaviour you can design against, stated concretely.

The trigger persists both the cron expression and timezone.

A worker scans due schedule triggers and records firing outcomes.

Timezone rules can produce skipped or repeated wall-clock times around daylight-saving changes; catch-up review makes missed occurrences explicit.

Complete the operating path

View all capabilities
Put it to workStart agents through an API trigger

Make a published agent part of your own application or service.

Put it to workUse your agents from Claude Code, Cursor and VS Code

Put the agents your team has built inside the coding assistants your team already works in.

Run it reliablyNever lose track of accepted work

Give every accepted unit of work a durable identity and history before execution begins.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Talk to us