Your agents. Your space. Your way.Captured in Astera
The agents you already love. Room to do more.
Claude Code
+
Codex
Bring your own accounts. Keep your familiar tools.
Built around the work that needs to keep going.
You set things in motion. Astera keeps them moving.
Carry context forward. See what depends on what. Keep the next step in view.
Smart Resume + Account rolling
A fresh session. A clear handoff.
When a limit triggers an account switch, Smart Resume gives the new session a compact checkpoint: your recent requests, changed files, git state, and where the conversation left off. The next agent starts with the work in view.
Your intent
Recent requests, in order
Your changes
Touched files and git state
Where you left off
Last command and recent exchange
Choose Smart Resume in Settings. Standard resume keeps the conversation history; Smart Resume starts fresh with the checkpoint.
Recorded in Astera: a usage limit triggers an account switch, and the same conversation continues.
Visual orchestration
See how the work comes together.
Follow Claude and Codex in a dependency graph. See what can run together, what is waiting, and which checks must pass. Open a Run to compare worker reports with changed files and diffs read from git.
Build the auth moduleClaude Code Done
Write regression testsCodex Done
Checks passed. Ready for the next task.Verified
Recorded in Astera: follow task dependencies, worker progress, validation, and cross-vendor review.Learn to read the Jobs graph
On your schedule. In your Slack.
Set a time for your session to start. Get a Slack notification when a turn finishes, and reply to keep the conversation going. Your desk is optional.
Scheduled session03:00
#
Astera APP
Your scheduled turn is complete. Check the update or reply to continue.
03:24
Recorded in Astera: the scheduled command is sent automatically when its start time arrives.
Illustrative workflows. See the real app in the demos.
✦
From an idea to a checked result
Beyond “I’m done.”
Ask a coordinator to turn your goal into tasks for Claude and Codex. Follow the run in Jobs, with tests and cross-vendor reviews attached to the work.
/astera-orchestration
Have Claude refactor sign-in, then have Codex add regression tests. Run the tests and review the result.
Break work into tasks. Add dependencies, tests, and review requirements.
02
Let the right agents get to work.
A coordinator dispatches ready tasks to Claude and Codex, and keeps track of progress.
03
Check. Refine. Check again.
With auto-fix enabled, failed checks and blocking review findings return to the worker for repair, until the checks pass or the retry limit is reached.
Astera 1.5.0
Set up once. Stay in control.
Share the tools. Choose how agents run. See what needs attention.
MCP & Skills
Add tools once for your accounts. Share a local MCP server across sessions in one project, or give each session its own when state must stay separate.
Choose a profile’s sandbox for folder and credential restrictions. Check platform coverage: Claude on Windows protects file tools only, with an unrestricted shell.
Give Astera a GitHub issue. It plans the work, runs isolated workers, and verifies the result locally. Turn on Carry it through GitHub to push the Run’s branch, open a draft pull request or bind the open one, and follow CI.
Code failures go back to an agent with the failed job’s log. Failures outside the code can be rerun within your limits. When a decision needs you, Astera asks.
One pull request headLocal checks → GitHub CI → Astera review
A second agent reviews the whole pull request
Merge-readyYou choose when to merge
Merge-ready applies to the current PR head only when local checks, required CI, and Astera review converge. A new push, failing check, changed base, or closed PR withdraws it. Astera never merges.
Remote Runtime
Close your laptop. Keep the work running.
Run Claude, Codex, and Jobs on another computer. Your laptop controls the work; the Runtime keeps the agents, worktrees, and checks running when your laptop sleeps or disconnects.
Pair over your own LAN, VPN, or Tailscale with an encrypted connection. Choose the Runtime in Astera, or reach it through the CLI and MCP. No Astera relay or cloud service is required.
Compare a Runtime’s setup and expected extensions from Details. Unpairing a controller pauses the Jobs it scheduled; a person on the Runtime decides when to resume.
Keep the Runtime computer awake and its Host running. Pairings are read-only by default; full control lets you start and manage work.
Headless CLI
Your terminal. The whole workflow.
Start Claude and Codex, run Jobs, and follow checks from your shell—with the app window closed. The local Host dispatches workers, manages worktrees, and keeps configured validation, review, and account rolling moving.
Plan with /astera-orchestration, run from the terminal, then reopen Astera to see the same work in the Jobs graph. JSON output and exit codes connect it to your own scripts.
Install the command once in Settings → CLI, then open a new shell and run astera version.
# Start the local Host
astera host start
# Pick a Job, then start a run
astera jobs list --human
astera jobs run --id JOB_ID
# Follow the returned run ID
astera runs follow --id RUN_ID --human
astera runs checks --id RUN_ID --human
Replace JOB_ID and RUN_ID with your IDs. Requires a configured, awake computer and a running Host.
Astera over MCP
Your agents. Your Astera workflow.
Connect Claude Code, Codex, or Cursor to Astera's local Host through MCP. An agent can create and follow Jobs, inspect checks, and read How It Works records. Optional access also lets it use sessions and GitHub.
Register a local client from Settings → CLI. For another device, the optional token-protected HTTP entrance uses the same tools and access settings.
Session access, GitHub writes, and HTTP each have their own setting and are off by default.
The client calls these MCP tools. Jobs also appear in the Astera app and CLI.
Astera Host
Close the app. Come back to the work.
A separate local Host keeps its Terminal and Chat processes running when Astera quits. Reopen the app to reconnect. If a Job worker or check is lost, the Host can recover it without waiting for the app to open.
For host-managed sessions on an awake computer. The Host can handle scheduling, account rolling, and Job coordination. See the CLI guide for scheduling limits.
Everything within reach
Stay in your flow.
Your code, browser, and terminals. Finally in the same place.
A workspace that fits you
Put sessions and files side by side. Split and arrange panes around the way you work.
Separate branches. Clear progress.
Give each task its own worktree. Keep changes isolated and pull request status in view.
Point to what you mean
Pick an element in Design Mode. Send your notes, its details, and a screenshot straight to a session.
Creative Hub
Keep multiple Higgsfield accounts in Settings and choose the one your agents use. When credits run short, the agent asks before switching.
Astera is a desktop workspace for Claude Code and Codex. Smart Resume carries context between accounts, Jobs makes coordination visible, and completion checks tie progress to test and review results. A local host can keep its sessions alive across app restarts.
Is Astera free?
Yes. Astera is free and open source under Apache-2.0. You bring your own Claude Code or Codex accounts. Any fees for those services are separate.
Which platforms are supported?
Windows 10 and 11, macOS 12 or later, and Ubuntu 22.04 / Debian 12 or later. See the installation guide for platform-specific steps and current release notes.
Can I use my existing accounts?
Yes. Connect your installed Claude Code or Codex CLI and the accounts you already use. Add multiple accounts, and Astera can resume work on the next available account for the same service when a usage limit is reached.
Will every job finish automatically?
Completion is not guaranteed. Jobs can repeat repairs and checks within the completion policy and retry limit you set. Questions that need your judgment still wait for your answer.
