Preview, edit, and save local files

Identify the file you are viewing#

Onevium opens local files from links in chat and from the project file list. Check the path at the top: editing a project file changes the original on disk, while an uploaded attachment may be a copy.

Use a practice project's notes.md containing a couple of ordinary notes. Choose a file that another task is not already editing.

Open the target file#

• Click Browse all files at the top of the conversation and select notes.md.
• You can also click a local file link in an assistant reply. References containing line numbers can locate particular content.
• In an open file, use the segmented path at the top to navigate directories or choose a neighboring file.

Check the path and content before editing. If access is missing, a file moved, or a temporary file expired, follow the panel's guidance to select the correct file again. A matching filename alone is not enough.

Edit Markdown and save it#

1. Open notes.md. Eligible Markdown files support editing in the preview surface; Source lets you inspect and edit the underlying text.
2. Append “Next: review the payment callback tests.” Unsaved changes at the top means the edit is still a draft.
3. Click Save, or use ⌘S on macOS / Ctrl+S on Windows or Linux while the file editor is focused.
4. Wait for Saved, then reopen the file to verify. If saving fails, read the error; text visible in the editor is not proof that it reached disk.

Saving a file does not commit it to Git. Use View changes, or follow Files, terminal, and Review, to inspect the scope of the change.

What each format supports#

For a CSV exercise, change one value in the source while preserving separators and quotes. Return to the grid and check that columns still align. A grid preview is not an Excel editor.

When another task changes the file#

An assistant, terminal command, or external editor can change the same file. The panel may then report File changed on disk or a conflict.

• Without unsaved edits, reload to see the current disk content.
• With a draft, preserve the text you need before deciding how to merge. Do not repeatedly save over another change while a conflict is reported.
• Reload from disk can discard the unsaved draft; read its confirmation first.

For concurrent tasks, use different files or separate working directories. Two split conversations pointing at the same directory still share its files.

Verify the saved result#

For a Git project, run this in the target project's terminal:

git diff -- notes.md

Confirm that only the intended line changed. For a non-Git project, reopen the file or check it in an external editor. A successful edit does not mean the entire project passes its tests.

Troubleshooting#

Next steps#

Use Review and the terminal to inspect file changes, or Input tools for attachments, file references, and queued messages.