Turn issues into action.
Dev preview
THE AGENT WORKSPACE / MAC EDITION
Less juggling.
More building.
Run your agents. Review their work.
Build your own tools. All on your Mac.
Your CLI subscriptions. Your workspace. Your call.
WORKSPACE / 001DEVELOPMENT PREVIEW
Less tab chaos.
More headspace.
Bring the tools you already use.
- Codex CLI
codex - Claude Code
claude - GitHub Copilot CLI
copilot - Antigravity
agy - Plain shell
shell
Bring your own authenticated CLI. Capabilities vary by tool.
01 / THE WORK, IN FOCUS
A little order.
A lot more possibility.
Plan it. Inspect it. Make it yours.
Actual UI. Fictional sample work.
Details, not detective work.
Dev preview
A home for the details.
Dev preview
Captured from repository UI components in an isolated, read-only fixture. Sample records; no live agents or customer data. Tracker and mini-apps are development previews.
02 / PUT IT TO WORK
Same workspace.
Your kind of work.
Start with one recurring task.
Make the next morning lighter.
Wake up to progress.
Schedule a focused coding task. Review what comes back.
Explore workflow →Catch it before customers.
Repeat regression checks. Keep the evidence close.
Explore workflow →Many clients. One cockpit.
Separate project environments. Less context switching.
Explore workflow →Keep the backlog moving.
Prepare issue triage and dependency checks for review.
Explore workflow →More making. Less admin.
Turn local source material into drafts you can refine.
Explore workflow →Make room for the big idea.
Give repeatable work a routine. Keep decisions yours.
Explore workflow →Workflow examples, not guaranteed outcomes. Setup, tools and review requirements are listed for each audience.
Find your fit · all ten audiences
Who it is for
Ten focused starting points. Each page names three workflows, what must be connected, what comes back, and what still needs human review.
-
Developer
Review-gate jobs return work for you to read before it reaches main.
Make progress on the boring half of my backlog while I sleep, and never let it touch main without me reading it first.
Read the Developer case -
Open-source maintainer
Wake up to triaged issues, a reproduction video, and a changelog you only have to approve.
Read my issues before I do, try to reproduce the bugs, and draft the answers — but never post anything in my name.
Read the Open-source maintainer case -
QA / Tester
Every morning, last night's test run — as screenshots, not a wall of red text.
Run the boring pass every night on a clean environment, and show me pictures, not a log.
Read the QA / Tester case -
Indie hacker / founder
AgentCron runs the chores; you make the calls.
Run the company's chores overnight so my day is only the thing nobody else can do.
Read the Indie hacker / founder case -
Agency / contract shop
One machine, six client repos, and one place for run output and available command evidence.
Keep every client repo moving and give me evidence of what happened, per client.
Read the Agency / contract shop case -
DevOps / platform
The infra chores you keep deferring, done overnight — as a plan you approve, never an apply.
Do the infrastructure chores I keep deferring, propose the change, and never apply anything.
Read the DevOps / platform case -
Tech lead / senior IC
Every change arrives with its own explanation. You review the reasoning, not the diff.
Do the first read for me, and make agent-written code explain itself before it reaches my eyes.
Read the Tech lead / senior IC case -
Content creator
Monday morning: the calendar planned, the drafts written, the week's posts queued. You publish.
Keep the calendar full and the next three pieces drafted, so I sit down to edit rather than to start.
Read the Content creator case -
Customer support lead
Every morning: the replies already written, and the three that genuinely need you.
Read the queue before I do, draft the obvious answers, and pull me in only for the ones that actually need me.
Read the Customer support lead case -
Analytics engineer
Your models ran overnight. Here's the diff that fixes the one that broke.
Run the models overnight, tell me what changed in the numbers, and give me the fix as a diff.
Read the Analytics engineer case
03 / A SIMPLE RHYTHM
Set the routine.
Stay in the loop.
Automation for the repetition.
You for the judgement.
- 01 / CONNECT
Bring your agent.
Choose a CLI and a project.
- 02 / SCHEDULE
Give it a rhythm.
Define the task. Pick the time.
- 03 / REVIEW
Make the call.
Inspect output. Decide what ships.
Your Mac must be awake and the app running. Approval gates protect workflows that call them; they are not universal tool interception. Know the boundaries ↗
04 / THE APP DEVELOPMENT KIT
Missing a tool?
Make it.
Your workflow deserves more than a workaround.
Build a mini-app with its own UI and SQLite database. Let agents use only the data and actions you grant through the app broker.
A client hub. A release checklist. A research notebook.
Your next tool starts here.
Local Dev preview. Production app installation is not yet enabled. Ideas above are apps you can build, not bundled integrations.
START WITH THE CONTRACT
agentcron apps sdk --jsonUse the exact CLI path from your installation.- 01▤
Your interface.
A purpose-built place to work.
- 02▥
Your app database.
Separate SQLite. Versioned migrations.
- 03↗
Granted agent access.
Declared records. Explicit actions.
STARTER TEMPLATES
Notes / Tracker / Dashboard
05 / BUILT IN THE OPEN VIEW
The product.
And the possibility.
A clear view of what exists.
An honest view of what comes next.
Your local control room.
Agent schedules, terminals, worktrees and review tools.
Explore the foundations ↗A workspace that grows.
Tracker, mini-apps and paired local-network mobile control.
See the preview boundaries ↗Further, together.
Internet remote access, deeper GitHub integration and a reports library.
Follow release progress ↗SMALL ROUTINES. BIG POSSIBILITIES.
Give your agents
a place to work.
Meet AgentCron. Your Mac’s next chapter.
See release status ↗Find your first use case →Preview showcase. Public downloads and checkout are not open.