Astron plans, calls tools, gathers observations, and keeps going until it has an answer. When a decision changes the outcome, or an action leaves the workspace, it pauses and asks.
Load context, choose tools, execute the safe ones, collect what came back, ask when necessary, then produce the output and persist the run.
Steps
11
Tools
6
Elapsed
48s
The pause is persisted in the database with the proposed action, its payload, and your answer. Approving resumes the same run from the same step.
Send this Slack update?
#product-team, 12 recipients, not reversible
Blocked this week: auth session refresh (waiting on review), billing webhook retries, and the onboarding copy pass. Two items need a decision from you.
Approval state lives in the run, not the interface. Cancel and the action never happens.
Tool registry
DuckDuckGo search and SSRF-protected page reading, separated so a search never fetches an arbitrary URL by accident.
List and read workspace files, create and edit artifacts.
Search an imported repository, inspect files, explain architecture, propose changes and diffs.
GitHub, Gmail, Google Calendar, Google Drive, Slack, Notion, and Linear once their credentials are configured.
Precise arithmetic, dates and times, structured data handling, and file parsing.
Astron detects scheduling intent, builds the cron expression and timezone, states what the run will produce, and stores it only after you approve.
| Task | Status | Schedule | Tools |
|---|---|---|---|
| Weekly blocker review | Active | Mon 9:00 AM | workspace, search |
| Competitor watch | Active | Daily 7:30 AM | search, artifacts |
| Release notes draft | Paused | On release tag | github, artifacts |
| Inbox triage | Draft | Weekdays 8:00 AM | gmail |
Create a workspace, name your coworker, and give it something you have been putting off.
Get Astron