Attach context
Drop a file or paste an image into Chat to include its path in your message. Describe what the agent should look for or change alongside the attachment.
Get to know Astera.
One place for your agents.
A clear path from an idea to finished work.
Astera is a desktop workspace for Claude Code and Codex. Start with one session, carry context across account limits with Smart Resume, and coordinate larger work through a visible Jobs graph. Use the orchestration skill when you want an agent to manage the steps.
- Account
- The Claude Code or Codex login a session uses.
- Session
- One conversation with an agent in a project folder.
- Job
- A set of tasks, with agents and checks working toward one objective.
What would you like to do?
Work with an agent on my projectSessions Keep going when an account hits a limitAccount rolling Give the next session the context it needsSmart Resume Run a prompt on a scheduleScheduling Split a larger task between agentsJobs Return to live sessions after an app restartAstera Host Understand what changed and whyHow It WorksYour first session
Start with one project and one account. You can explore automation after your first conversation is running.
Install Astera and your agent
Use the Download button to get the installer for your operating system. You also need Claude Code, the Codex CLI, or both installed and available on your PATH, so Astera can start them.
Astera runs your existing tools. Accounts and any usage fees for those services are separate.
Platform-specific installation stepsConnect an account
In Accounts, use Auto-detect to find existing accounts and register the ones you want. Or choose Add account to create a separate account entry, then complete its sign-in when prompted.
Choose your folder and session type
Open New session. Select your Project folder and Account, choose Terminal or Chat, then click Start. A folder keeps the conversation connected to the code you are working on.
Give the agent a clear first task
Describe the result you want and how to check it. For a first look at an unfamiliar project, try:
Explain how this project is organized and how to run it locally. Don’t change any files yet.
Read the response, answer any questions, and continue in the same session.
Terminal or Chat. Your choice.
Both give you a session with your agent. Choose the interface that feels natural for the work you are doing.
Terminal
The familiar CLI inside Astera. Use it when you want to work directly with the agent’s terminal interface.
Chat
A conversation with a message composer. Questions and approvals appear as cards; model and permission controls sit beside your message.
Choose before you start. A session keeps the type it was created with. Set the default in Settings → General → New sessions start as, or choose a different type in New session.
Resume from history
Open Accounts and history and expand your project. Click a conversation to preview it, or choose its Resume session button, select an account, and click Resume to continue working. If the folder moved, select its current location when prompted.
Find a hidden project
Use Settings → History → Unhide to return a hidden project to the history list.
Continue on your next account
Account rolling moves a session to another available account for the same service when it reaches a usage limit. With the standard resume strategy, the conversation continues on that account.
- Register and sign in to the accounts you want to use.
- In New session, choose the first account. Use + Add account to set the next accounts in the rolling order.
- Start the session. Astera watches for a limit and switches when another account is available.
Every account still has its own limits. If none is available, check the displayed reset time. The session’s Wait for the limit to reset, then resume automatically option controls waiting and resuming with a single account; rolling is automatic with multiple accounts.
When adding an account, Import settings from the default account can bring over its setup. Review the import dialog: merge and replacement rules depend on the file and provider. Imported settings apply to new sessions.
Smart Resume. Carry the context forward.
Use Smart Resume when an account switch should give the next session a focused handoff. Standard resume continues the existing conversation. Smart Resume starts a fresh conversation with a compact checkpoint of the work so far.
- In Settings → General → Session resume strategy, choose Smart Resume. It is off by default.
- Set up your account rolling order. A limit-triggered switch to an available account for the same service uses the checkpoint.
- Continue in the session. The next agent receives the checkpoint as its first message and can inspect the working files to pick up the task.
What you asked for
Recent requests stay in order, alongside the tail of the exchange. The handoff includes what the session was being asked to do.
What changed
The working folder, git state, touched files, and last command provide concrete starting points. The checkpoint is a compact handoff, not a complete copy of the conversation.
Context for Job workers
For Job workers, available task state adds the objective, dependencies, recent reports, decisions, and validation context. The next worker can see both its task and the surrounding work.
If the checkpoint cannot be built, Astera uses standard resume. Smart Resume does not remove account limits, and a compact handoff can omit older details. Keep essential requirements in project files the agent can read.
Give a session a schedule
Use the scheduler for recurring work, such as checking a test suite every morning or asking for a regular project update.
- In New session, enable Scheduler.
- Choose an interval, or a daily, weekly, or monthly schedule.
- Enter the command for a Terminal session, or the prompt for a Chat session. Start the session to activate it.
Keep Astera running and your computer awake for scheduled work. A scheduled session sends work to one conversation. For a sequence of dependent tasks, use Jobs.
Follow the work from Slack
Receive progress updates when a turn finishes, an account reaches a limit, or your input is needed. With bot mode configured, each session has its own thread. Reply in that thread to send a message back to the session.
- Create a Slack app and invite its bot to your notification channel.
- Enter the bot token and channel ID in Astera’s Slack settings. For replies, also configure Socket Mode, its app token, and your Slack member ID.
- Turn on Slack progress notifications for the session.
Your member ID enables replies. Only the configured Slack member can send input to a session. If the member ID is empty, replies are not delivered.
Follow the complete Slack setup
Bring agents together with Jobs
Opt-inA Job turns an objective into a graph of tasks. Its connections show what can run in parallel and what must wait. Follow Claude and Codex workers, questions, and completion checks from the same run.
Example: update the sign-in flow
Implement the changeWrite regression tests
Both tasks finishRun checks & review the resultRead the connections
Dependencies determine when a task is ready. Tasks with no unfinished dependencies can run together within the concurrency setting.
See why work is waiting
A task can be running, validating, reviewing, or blocked by a Gate. Open it to inspect its state, worker, and any question that needs an answer.
Follow the checks
For a task with checks, the worker’s completion report starts validation. Dependent tasks wait for the required checks and review to pass. The timeline lets you follow the sequence.
- Enable Agent orchestration in Settings. Use a git repository with at least one commit and a branch checked out.
- Open Jobs → New job. Enter the Objective, choose a Coordinator account, and set Run at once.
- Add tasks, worker accounts, and dependencies. Attach build, test, or cross-vendor review checks. Enable Auto-fix until the checks pass if you want repair attempts within the retry limit.
- Click Run. Follow the graph, answer questions, and review the finished work. For a normal Job, click Merge when you are ready to bring it into your project.
“Done” is checked, not assumed. Failed checks can go back for repair, but a retry limit or a decision that needs you can stop progress. Normal Jobs keep changes in worktrees until you merge them.
Can I ask an agent to coordinate a Job?
Yes. The /astera-orchestration walkthrough shows how to give a new coordinator session an objective, worker roles, dependencies, and checks. Its run appears in the same Jobs sidebar.
How are scheduled Jobs different?
A scheduled Job is a template that creates a separate run at each scheduled time. Missed times while the app is closed are skipped. Results are not automatically merged into your project, and completed runs clean up their worktree folders. See the Job lifecycle reference before setting up recurring changes.
Give the goal. Let an agent coordinate.
/astera-orchestration gives an Astera session a way to supervise multi-step work across Claude and Codex. The coordinator creates tasks, dispatches workers, waits for reports, and brings decisions back to you. The run stays visible in Jobs.
- Enable Agent orchestration in Settings, then open a new coordinator session in your project. Skills are loaded at session startup.
- Describe the objective, which agent should do each part, the order, and how to check the result. Register usable accounts for the providers you request.
- Open the project’s Jobs sidebar to follow the graph. Read questions and Gates when the coordinator needs a decision. Review the result before bringing changes into your project.
/astera-orchestrationRefactor the sign-in flow with Claude. After that, have Codex add regression tests. Run the project’s tests and request a cross-vendor review. If checks fail, repair and check again within three attempts. Ask me when a decision is needed.
Use it when coordination matters. Dependencies, worker reports, and completion checks make it useful for larger work. A single small task can stay in a normal session. Cross-vendor review requires a usable account from the other provider and uses its quota.
Astera Host. Keep the session alive.
Astera Host is a separate process on your computer that can own Terminal and Chat sessions, project terminals, and Run processes. When it owns a process, quitting the app leaves that process running. Reopening Astera reconnects to supported live sessions.
Return to the same work
Reopen Astera after an ordinary quit to reconnect to a surviving session and its buffered output. This is the live agent process continuing, rather than a new conversation started from history.
End sessions deliberately
Stop a session when its work should end. Where the tray menu is available, Quit and end sessions ends host-managed sessions as well as quitting the app.
Keep automation running
Keep Astera running and the computer awake for scheduling, account rolling, Slack integration, and Job coordination. A surviving agent process does not mean those app services keep running after you quit.
Check the quit or update notice. Sessions started without the host can end with the app. Reconnection after a version update depends on compatibility. Host does not keep work running through computer shutdown or sleep.
Understand what changed. And why.
How It Works turns a finished piece of work into a readable explanation. Keep your original request beside an overview of the change, a flow diagram, the reasons behind decisions, and the files involved.
- In Settings → General, enable Work unit tracking and choose an Explanation account to write the explanations.
- Open a new session in a git project. Send
/astera-taskfollowed by a concrete objective, such as “Add Google sign-in and verify that signing out ends the session.” - Continue in that conversation. The skill tells the agent to record the start and finish of the task, even when the work takes several messages.
- Open How It Works from the sidebar, or press Ctrl/Cmd + Shift + H. Select a completed record to read its explanation in a pane tab.
Start with the result
What it does explains the change in plain language. What you will notice describes its effect on the product. Your original request stays below the title so you can compare the outcome with what you asked for.
Explore the flow
Select a flow step that has references to see its description, reasons, and related files. Show all returns to the full explanation. Some changes have no meaningful flow or visible effect, so those sections may be absent.
Follow the reasoning
Why it works this way explains decisions and their sources. Implementation groups the related files by role; click a filename to open it. In a narrow pane, use Reference to open the reference drawer.
A record is an explanation, not a test result. Recorded means the write-up is available. Read the separate verification line to see what passed, failed, or was only partly checked. Normal session checks are reported by the agent; Jobs carry validation results from their Run.
What do the record states mean?
In progress is an open task. Left unfinished means recording was interrupted; read the reason. Writing up means the explanation is being generated. Recorded is ready to read. For Needs review or Could not write it up, read the reason and check the verification result before continuing.
Write it up again regenerates the explanation. It does not repair code or rerun tests.
Why is my work missing?
Enable tracking before starting a new session, choose an Explanation account, and declare the task. Earlier conversations are not imported, and work that changed no files produces no completed record. Only one task can be recorded per session at a time.
Claude Code’s /goal closes its record automatically; with Codex’s /goal, mark it Done yourself. Completed Jobs Runs are also recorded when tracking is enabled. If writing failed, resolve the stated cause and use Write it up again.
A few more possibilities
These features are off by default. Turn them on when they fit the way you work.
Smart Resume
Choose a checkpoint-based handoff under Settings → General → Session resume strategy. The Smart Resume guide explains what carries forward and when standard resume is used.
How It Works
Enable Work unit tracking and choose an Explanation account to turn completed work into readable records. Follow the recording and reading guide for setup, flow diagrams, verification labels, and troubleshooting.
Agent browser
Enable Agent browser, then start a new session. Ask the agent to check your local web app. It can open its own preview tab, inspect the page, and check console and network errors. It works with local development pages.
Keep the rest of your work close
Files & split panes
Open files beside the session changing them. Split right or down to compare work. The explorer shows git status and offers file actions such as rename, copy, and reveal in your file manager. Use the project terminal to run commands yourself.
Markdown preview
Open a Markdown file, then press Ctrl/Cmd + Shift + V to cycle between editor, split view, and preview. In split view, the editor and preview follow each other’s scrolling.
Restore a deleted file
For a deletion captured by Astera, right-click in the explorer and choose Local History…. Select the item and click Restore. If its old path is occupied, the restored copy gets another name. Snapshots are kept for up to 30 days within the project’s size budget; items over 50 MB are excluded.
Run your project
Select a configuration in the Run toolbar to start a dev server, build, or test, then read its output in the Run console. Astera detects supported scripts and tasks, including npm scripts and standard Gradle/Maven tasks. Detected configurations appear in italics; edit one to save it as your own.
Worktrees & pull requests
Choose Start in a separate worktree when creating a session in a git repository with a commit and branch. Work on the isolated branch, then use the worktree list to review PR state. Once the branch has new commits, its create-PR action can push it and open a pull request using your existing gh login. Review the target branch and details in the dialog.
Design Mode
Open your web page in a tab and turn on Design Mode. Pick an element, describe what should change or ask a question, then choose Send to session. The agent receives your note, element details, and a cropped screenshot. A tab holds up to twenty notes; navigating away turns Design Mode off.
Make Astera feel like yours
Appearance
Open Settings → Appearance to choose one of seven themes and set your terminal font separately. Theme changes update open terminals while preserving their scrollback.
Language & shortcuts
Under Settings → General → Language, choose English, Korean, Japanese, Spanish, or System. Open Settings → Shortcuts to inspect and remap the controls.
Desktop notifications
In Settings → Notifications, choose alerts for input needed, waiting on a limit, and account switches. These help you follow a session while you are looking at another session or window.
App updates
Open Settings → Info → Check for updates and follow the available download/install action. Update support depends on your platform and build. When automatic updates are unavailable, download the matching installer from GitHub Releases and follow the installation notes.
A few useful answers
Do I need both Claude Code and Codex?
No. Start with either one. Add the other when you want to work with both, including reviews across vendors.
Why can’t I start a session?
Check that you selected a project folder and account, and that the matching CLI is installed and can run in that folder. If you just installed it, restart Astera so it can detect it.
Why is a Job waiting for me?
Open the Job and read its question or Gate message. It can need a usable account, a git branch, a decision, or help after a check fails. The message explains what is blocking progress.
Where can I change themes and keyboard shortcuts?
Open Settings. Appearance offers seven themes and separate terminal font settings. Shortcuts lets you remap the keyboard controls. The app supports English, Korean, Japanese, and Spanish.
Useful shortcuts
Use Cmd on macOS and Ctrl on Windows or Linux. These are the defaults; you can remap them in Settings.
- Explorer
- Ctrl / Cmd + Shift + E
- Jobs
- Ctrl / Cmd + Shift + J
- How It Works
- Ctrl / Cmd + Shift + H
- Markdown view
- Ctrl / Cmd + Shift + V
Ready for your first session?
Start with a folder, an account, and an idea.
Still need a hand? Ask on GitHub or explore the technical documentation.