Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runable.com/llms.txt

Use this file to discover all available pages before exploring further.

You open Runable. You type what you want built. The agent builds it. That is the entire premise. You do not need to describe how to do it, which tools to use, or what steps to follow. Describe the outcome. The agent handles everything else.

The loop

Every interaction with the agent follows the same cycle: describe, answer, review, iterate. You type your goal in plain language and hit send. The agent reads your message, figures out what information is missing, and asks before it starts. You answer once. It builds. You see the result live in the right panel and keep talking to refine it.

What that looks like in practice

Ask the agent to build a booking site for your fitness studio

The agent asks about things you did not specify: do you need Stripe checkout for the memberships? Should the schedule pull from a database or be static? Do you want a map embed for your location?You answer. It scaffolds the project, writes the code, starts a live preview, and shows it to you in the side panel. You say “make the pricing cards horizontal instead of stacked” and it updates in place.

The agent asks first, and the it builds

Most AI tools take your prompt and immediately generate something. If it is wrong, you start over. Runable asks clarifying questions before building anything. That means the output matches what you actually meant on the first try.
You do not need a perfect prompt. A rough description is enough. The agent fills in the gaps by asking you.

You watch it work in real time

While the agent is running you can stop the agent at any time with the stop button. It halts immediately. If your connection drops while the agent is working, it keeps going in the background. When you reconnect, the stream picks up where it left off.

Every chat gets its own sandbox

Each Agent Mode conversation runs in an isolated sandbox environment. The agent can write code, run commands, install packages, and start servers inside it. Your sandbox persists across messages within a chat, so the agent can build on previous work without starting over. The sandbox auto-pauses after 45 minutes of inactivity and resumes when you send your next message.

The agent remembers your preferences

Every new chat, the agent checks its memory first. If you have told it your preferences before, it already knows them.

Tell the agent your brand defaults once

Every website, deck, carousel, and image starts from those defaults. Preferences change ? Tell the agent and it updates.

The agent uses skills automatically

When you ask for something specific, the agent loads the right skill, a pre-built workflow with tools and steps for that job. You never need to pick skills manually unless you want to. To use a skill explicitly, type / in the input bar and select one from the dropdown.

Use Plan Mode for complex projects

Plan Mode interface showing the agent's structured plan with steps, tools, and verification method
For projects with multiple moving parts, click Plan in the input bar before sending your message. The agent researches your request, asks clarifying questions, and writes a structured plan showing what it will build and in what order. You review, adjust, and approve before it starts.
Use it any time your project has more than two or three pieces that need to work together: a website with authentication, payments, and a database. A multi-page report with specific data sources. A workflow that chains multiple tools. Plan Mode catches misalignment before it becomes wasted work.

Next steps

Agent Mode vs Chat Mode vs Plan Mode

Understand when to use each mode and what each one can do.

Branching and Rollback

Go back to any point in a conversation or fork it into a new direction.

Memory

Set your preferences once and have the agent remember them in every conversation.

Skills

Learn how the agent uses skills and how to create your own.