Who handles coding tasks

What you see

Updated Apr 26, 2026Plain text →

What you see

Coding tasks go to Dev. You don't have to ask for him by name; Astra brings him into your CEO chat panel when you describe a build, fix, integration, or deploy.

The handoff in chat

When the work moves, Dev's avatar appears in your chat thread alongside Astra's bridge message ("Bringing Dev in to wire up Stripe"). A Task Card opens with his name on it, and his messages in the thread show his name and role. Live URLs and code links land on the card as Assets when the build is done.

How to use it

  1. In the CEO chat, describe what you want to exist. Examples:
    • "Build me a quick prototype that does X."
    • "Add Stripe checkout to our signup flow."
    • "Fix this bug." (paste the error)
    • "I want a landing page that does Y."
    • "Deploy our latest changes."
  2. Open the Task Card from the chat to see what got built, where it lives, and how to test it.

What you'll get back

Working code, deployed live. Each delivery includes a test URL on the card, a one-line summary of what changed, and a note on follow-ups.

How the team coordinates around this

If the build needs copy, Casey appears in the same Task Card thread. If it needs a design polish pass, Astra queues a design review on the same card.

Still have a question?
Ask Astra in chat — she has the same docs you do.
Open chat
Related