Skip to main content

Documentation Index

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

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

Writing is a vertical workbench tuned for long-form prose — articles, reports, posts, technical guides, internal docs.

​
Workspace

The Document workspace pairs a Markdown file tree with an editor:
ElementWhat it does
File treeOutputs are organized as Markdown files (outputs/your-doc.md). Search by name, or open the underlying directory with the folder icon
EditorThe document content. The top-right has a Read / Edit toggle, a Latest Workspace file selector (switch between versions of the doc), and Export (export as PDF)

​
Creating a document

1

Switch to Writing

In the input box, click the workbench switcher (defaults to General) and choose Writing.
The default workbench can be changed in QoderWork settings — set Writing as your default if it’s the surface you live in.
2

Brief the agent

Describe the topic, audience, tone, and key points. Click the microphone for voice input.
3

Read or edit on the canvas

The output appears as a Markdown file in the outputs/ folder. Toggle Read in the top-right to review the rendered Markdown, or Edit to make direct changes in the editor.

​
Iterating

  • Add to the queue. Send follow-up instructions in the bottom input box — “add a section on permissions” — the agent updates the relevant parts of the file in place.
  • Stop a run. Click the stop button next to the input to halt generation mid-flight.
  • Compare versions. Use the Latest Workspace file dropdown to flip between the latest and earlier versions of a document — useful when you’ve taken multiple passes and want to compare.
  • Edit directly. Switch to Edit in the editor to fix a sentence or rewrite a paragraph yourself; the agent picks up your edits in subsequent turns.
  • Switch models. Use the model dropdown to change models for the next step.
The clearer the audience, the better the draft. “Internal post-mortem for the platform team, lessons-learned focused, no blame” lands far better than “write up the incident.”

​
Exporting

Click Export in the top-right corner to export the current document as a PDF file. You can also copy the rendered text into any downstream tool — docs, blog CMS, internal wiki, or chat.

​
Use cases

​
Technical guide from rough notes

@oss-notes.md
Turn these rough notes into a technical guide for engineers new
to Alibaba Cloud OSS. Cover core concepts, storage classes,
permissions, upload/download mechanics, lifecycle, monitoring,
and best practices. Use code examples and comparison tables.

​
Internal post-mortem

@incident-2026-05-19-timeline.md @slack-thread.txt
Draft a blameless post-mortem for the May 19 incident.
Sections: summary, impact, timeline, root cause, what worked,
what didn't, action items with owners. Tone: neutral, factual.

​
Release note from a PR list

@merged-prs-2026-w20.md
Write a customer-facing release note covering the highlights
from these PRs. Group as Features / Improvements / Fixes.
Keep each item to one tight sentence; lead with user impact.