v0.5.0 — In development

Astro sites at agent speed,
with studio control.

The desktop workspace for studios and freelancers who deliver Astro sites: run your agent on a client project, watch the page change, and read the diff before anything ships.

Join the waitlist See how it works

Internal build — the waitlist books a demo, not a download

The Astrology window: the page tree on the left, the live preview of the site being edited in the middle, and the inspector with the agent composer on the right.

Astrology editing this website: route tree, live preview and the agent composer in one window.

Works with Claude Code and Codex CLI · Git and GitHub CLI · Vercel, Netlify and Cloudflare

The agent is not the slow part

Astrology gives that afternoon back: the check happens in the same window as the change.

A turn ends in minutes. Reading what it touched takes the rest of the afternoon.
The preview, the diagnostics, the diff and the deploy each live in a different window.
It is a client's site, so nothing goes out on trust.

How it works

From request to deploy, without changing window

Four steps. The project folder, the agent account and the hosting keys stay yours.

01
Open the client project
Point Astrology at a project folder, or start one from an Astro template. It checks which tools your computer already has and can install the supported npm-based ones.
02
Ask, at the permission level you choose
Propose to talk a change through, Edit to let the agent write files, Autonomous for broader command access. The request runs in the Claude Code or Codex CLI you already use.
03
See what changed
Read the agent's output with the live preview beside it. Diagnostics and the Git change summary say what moved, and the next request starts from the same screen.
04
Ship it
Write the commit, push, build the site and deploy through your host's CLI. Each action keeps its own output and status.

Edit and Autonomous write to the project directly: changes are reviewed in the preview and in Git, not held in a per-file approval queue.

Step 02, up close

Ask for a change while you look at the page

A composer sits under the properties column. Context chips say which page is open and which element is selected, so the request can stay one sentence — and the answer arrives as code in your project.

Chips for the open page and the selected element
Propose, Edit or Autonomous, per request
Hand a failed build to the agent with its whole log

src/pages/blog/index.astroillustrative code

---
import Layout from '../layouts/Layout.astro';
import TagList from '../components/TagList.astro';
import { getCollection } from 'astro:content';

const posts = (await getCollection('blog'))
  .sort((a, b) => b.data.pubDate - a.data.pubDate);
---

<Layout title="Blog">
  <ul class="posts">
    {posts.map((post) => (
      <li>
        <a href={`/blog/${post.id}/`}>{post.data.title}</a>
        <TagList tags={post.data.tags} />
      </li>
    ))}
  </ul>
</Layout>

Step 03, up close

Everything you check before the client does

Structure, page, broken links, translations, history and deploy — the parts of a handover you cannot sign off without looking.

All 12 features

Your Astro workspace

Import a project folder or create a site from an Astro template. Keep your projects, preferred agent and deployment target together.

See your site structure

Explore routes, layouts, endpoints and detected content collections. The route tree updates as files change.

Preview and edit

Switch between the live page and its highlighted Astro source. Edit and save the full file internally, or change supported literal text and attributes directly from the preview.

Diagnostics and translations

Find missing images, broken internal links, translation gaps and dependency issues. Use the available automatic, agent-assisted or manual remedies.

Git and GitHub

Inspect repository status, a change summary and commit history. Commit, push and pull, or create a GitHub repository through GitHub CLI.

Build and deploy

Run production builds and deploy through Vercel, Netlify or Cloudflare CLI. Preview and production actions use your host account and project configuration.

Questions

Before you ask for a demo

All questions and licence terms

Can I see the app before it is released?

That is what the waitlist is for. Astrology is an internal build, so there is no public installer and no purchase yet: leave your details and you will be contacted when demo slots open. A demo is a walkthrough of the current build, run on a real Astro project.

Can I open an existing Astro project?

Yes. Choose its folder to add it to the workspace. You can also create a project from a template. Astrology works on the project files in that folder.

Which AI agents can I use?

Claude Code and Codex CLI. Install and authenticate the agent you want to use. Astrology runs that CLI; it does not provide an API-key form, an included model subscription or a local-model selector.

Does my code stay on my computer?

The working files stay in your project folder, but connected tools can send data over the network. Claude Code and Codex handle AI requests according to their configuration and provider policies. Git pushes and deployments send code or build output to the selected service.

See it on a project you are already delivering

Astrology is an internal build. Join the waitlist to be invited to a demo and to hear first when the studio licence opens.

Join the waitlist See pricing

Requires Node.js, npm and Git · AI features use your installed agent CLI

Astro sites at agent speed,with studio control.