ARIA IDE

Talk to your developer while it is working in the codebase.

ARIA IDE is the software-development workspace inside ARIA Agent. When a project is connected with approved tool access, you can have a natural, real-time, back-and-forth voice conversation while ARIA reads files, executes approved edits, investigates failures, applies fixes, runs checks and explains the work.

Start with ARIA Read the IDE docs

41 const session = getSession();

42−revokeAllSessions();

42+revokeOtherSessions(session.token);

43+await runAuthChecks();

44+"Auth checks passed"

Conversation + execution

You do not have to stop talking and convert the conversation into separate commands. Explain the problem, listen to ARIA's reasoning, interrupt, change direction, approve the next action and keep the same development conversation going while work happens.

Same ARIA identity

ARIA IDE is not a second assistant. It is ARIA Agent working in software-development mode, using the same account, project context and conversation while exposing code-specific tools and controls.

Voice-driven development

Back-and-forth conversation stays live while the project changes.

A developer should be able to speak naturally through the entire debugging or implementation cycle, not just dictate a one-time prompt.

Developer: The login works, but changing the password logs me out. Find out why.

ARIA: I found the session revocation path. It is revoking the current session with every other token. I can preserve the active token and still revoke the rest.

Developer: Do that, but don't weaken session security. Run the auth checks after.

ARIA: Understood. I'll keep only the session performing the password change, revoke the others, then run the checks and report the result.

Developer: Hold on — show me exactly what file you're changing first.

ARIA: Stopping before the edit. The change is in the authentication service and the change-password endpoint. I'll show the proposed diff before execution.

What ARIA IDE can do

A conversational development workspace, not a code-completion box.

Read the real project

Inspect files, structure, existing conventions and relevant context before proposing a change.

Edit with approval controls

Create or modify project files when the connected workspace grants the required action and the user approves sensitive changes.

Debug failures

Trace errors through the actual code and logs available to the workspace instead of giving generic debugging suggestions.

Apply fixes

Turn the diagnosis into scoped code changes, explain what changed and keep the developer in control of the work.

Run checks & tests

Execute approved project checks and use the real output to decide whether the change solved the problem or needs another iteration.

Review & prepare release work

Inspect diffs, risks, documentation and release readiness without silently shipping changes outside the user's approved workflow.

Interruptible

If the developer speaks while ARIA is explaining or preparing the next action, the conversation should be able to stop, listen and adapt. “Don't change that file,” “why are you doing that?” and “run the test again” are normal turns in the same session.

Project memory

Decisions, prior attempts and project context belong with the workspace so returning to a project does not mean explaining the entire codebase from zero.

Inside ARIA Agent

One assistant can move from business thinking to software execution.

Use ARIA Agent to research, plan and reason about the work, then open the project in ARIA IDE and continue the same relationship with direct development tools.

Back to ARIA Agent →