> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/prompting/debugging/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# Fixing a result that isn't right

> Correct the current result with a focused prompt, restore a version that worked, or make a precise change in the code editor.

When a result is close but not right, start with the smallest change that would fix it. You can ask
Mythos for a focused edit, restore an earlier version, or edit an exact value yourself.

## Describe what you can see

Name the location, the current problem, and the expected result. Do not ask Mythos to “make it
better” without saying what better means.

```text
On mobile, the pricing cards overlap the footer. Keep the cards in one column and add clear space
before the footer.
```

```text
In the hero, keep the current copy and button. Replace only the background image with a soft pink
gradient and increase the headline contrast.
```

If an action fails, include the action you took and the message or visible behavior that followed.

## Make one focused edit

#### Choose the problem to fix

Start with the issue that blocks review or use of the page. Leave unrelated
polish for a later message.

#### Protect what already works

Name any copy, layout, or behavior that must stay unchanged.

#### Send the correction

Describe the desired result in observable terms: what moves, what appears,
and what happens after an action.

#### Check the preview

Review the affected area at desktop and mobile sizes. Continue only after
this change is correct.

> **Tip**
>
> Several small corrections are easier to verify than one request that redesigns
> the whole product.

## Investigate a repeated problem

If the same problem returns after a focused fix, use [Plan mode](/features/plan-mode) to understand
the cause before changing more code. Include what you already tried and whether the issue happens
in Preview, on the published site, or both.

```text
The reservation is visible until I reload, then it disappears.
Investigate why it is not saved. Explain the cause and propose the smallest
fix before changing the app.
```

A connection failure and a code error need different remedies. Read any request to reconnect a
service or approve an action before sending another Build.

## Restore a version that worked

Use History when the current direction is worse than an earlier result.

#### Open History

Open the project’s **History** panel.

#### Preview an earlier version

Select the last version that looked and worked as expected.

#### Restore it

Choose **Revert**. Mythos makes that state current while keeping later
versions available in History. A revert changes project code; it does not undo data or actions
already sent to external services.

#### Try the change again

Send a narrower correction from the restored version.

## Edit an exact value yourself

Use the code editor when you already know the precise text, color, class, or number to change.
Direct editing requires a Pro or Business plan and permission to edit the project.

#### Open the file

Use the workspace file tree to find the relevant page or component.

#### Make the smallest change

Edit only the value you intended to replace.

#### Save and review

Save the file, then confirm the result in the preview.

Use chat for changes you can describe more easily than you can write, such as a new section,
workflow, or visual direction.

## Handle a failed edit

If Mythos reports that an edit failed before delivery, the previous working source remains current.
Read the message before retrying. If it says a save or restore is still being verified, use
**Check save status** or **Check restore status** first. If an external action has an uncertain outcome,
check the connected service before trying to repeat it. For a confirmed Build failure, reduce the
request to one clear outcome and try once more. If the same failure repeats,
follow [Troubleshooting](/reference/troubleshooting) or contact support with the project link and the
message you saw.

## Related

* [Writing good prompts](/prompting/writing-good-prompts)
* [Version history](/features/version-history)
* [Workspace editor](/features/workspace-editor)

> Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.