01
Open workspace or Central terminals
Shells for different projects become easy to confuse. Open workspace Terminals or Central, each with independent Split and Canvas layouts.
Aiola Terminals
Shell output, browser previews, and agent chats get scattered across windows. Aiola keeps them in saved Split or Canvas layouts with reusable workspace commands. Check each change beside the tools and references that explain it.
01
Shells for different projects become easy to confuse. Open workspace Terminals or Central, each with independent Split and Canvas layouts.
02
Switching windows separates errors from their visible effects. Add a terminal and browser, run your app, and open its local address.
03
Rebuilding your desk layout wastes time each session. Aiola saves panes, tabs, card positions, and sizes separately for each workspace and Central.
Navigating away should not interrupt a running command. Shell sessions stay attached, restore retained output on reconnect, and offer Restart after disconnection.
Several shells quickly outgrow one terminal view. Split horizontally or vertically, resize, move or swap panes, and rename or reorder tabs.
Previewing changes should stay close to your shell. Navigate URLs, reload pages, inspect developer tools, and copy screenshots into chat.
Remembering every development server port slows you down. Open detected local servers from browser cards and stop their terminal sessions or processes.
Transcribing paths and errors by hand invites mistakes. Drop files to upload and paste paths; copy, paste, or add selected terminal output to a thread.
Repeated development and test commands are easy to mistype. Save named actions in Workspace Settings, Environment, then launch them from the toolbar.
One-off checks do not need a saved action. Enter one command or several lines in Run command to execute them in the workspace terminal.
Layout bugs and stale sessions can hide a fix. Choose device sizes, rotate previews, adjust zoom, or clear browser cookies and cache.
A fixed grid can separate related work. Arrange terminal, browser, chat, image, and file cards; pan, zoom, or fit the canvas to view.
Agent answers lose meaning when their output is elsewhere. Start or open conversations and inspect response diffs beside terminals and previews.
References are easy to lose behind windows. Move and resize image or file cards, copy file contents, and switch supported files between source and rendered views.
A change can be easier to explain with a sketch. Draw shapes, connectors, freehand lines, text, and notes with adjustable styling.
Manually lining up every card interrupts your work. Apply grid, column, row, or main-and-side arrangements.
A crowded canvas can make references hard to read. Choose dots or a preset background behind cards and drawings.
Repeated mouse trips slow down terminal work. Configure shortcuts for terminals, browsers, and chats, or open Keyboard shortcuts from the header.
Errors and previews end up in different windows. Split layouts put terminals, browsers, and chats together. The embedded browser opens your local app beside its command output.
Restarting your layout wastes time. Persistent shell sessions retain running work as you navigate. Saved workspace and Central layouts restore their own arrangements.
Frequent commands are easy to mistype. Saved Run commands give recurring actions names in the workspace toolbar. Run command also accepts one-off commands and multiple lines.
Visual bugs need more than a desktop preview. Device sizes, rotation, zoom, screenshots, and developer tools help inspect a change. Clear cookies or cache when session state obscures the result.
Complex changes need visible references. Canvas cards keep images, files, chats, and terminals together. Whiteboard drawing and automatic arrangements help organize the explanation.
Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app. Every issue becomes a task an agent can take.