Skip to content

Add Dreaming page (best practices) - #18

Open
philipph-askui wants to merge 14 commits into
mainfrom
docs/dreaming
Open

Add Dreaming page (best practices)#18
philipph-askui wants to merge 14 commits into
mainfrom
docs/dreaming

Conversation

@philipph-askui

Copy link
Copy Markdown
Contributor

Documents the Dreaming feature: the Desktop App analyzes past test runs (grounded in their pass/fail outcomes) and proposes small, human-reviewed edits to a project's rules.md / test definitions, surfaced on the Dashboard.

  • New page: content/docs/best-practices/dreaming.mdx (registered in the section nav after Analyzing failures, its automated successor).
  • Mirrors docs/product/dreaming.md in the app repo.

Companion to askui/integrated-task-platform#203 — merge after the app PR.

🤖 Generated with Claude Code

philipph-askui and others added 6 commits August 7, 2026 06:58
Document the Dreaming feature — the app analyzes past runs (grounded in
pass/fail) and proposes reviewed edits to rules.md / test definitions, on
the Dashboard. Mirrors docs/product/dreaming.md in the app repo.

Companion to askui/integrated-task-platform#203 — merge after the app PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Broaden the list beyond rules + tests to ui.md, setup.md, teardown.md and
procedures/*; note device info stays with device profiles.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Note the Git requirement + per-edit commit so changes are revertable.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Note the experimental opt-in (warning + acknowledgement), the manual-backup
advice, that it won't change things when tests pass, and the progress ETA.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…anges

Note the 'N of M runs' confidence and the retrospective helped/hurt check with a
human-approved undo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@philipph-askui

Copy link
Copy Markdown
Contributor Author

Synced this page with the Dreaming work landing in desktop-app PR #203. Added: analysis cost (last-session cost + review-banner/page), the Extending → Dreaming tab (the opt-in moved here from Settings, plus model choice and an Analyze-now trigger), the best available model recommendation/default, the activation floor (only learns from runs made after you turn it on), the respects-your-own-edits behavior, and advisories for tool/SDK/environment faults that point to support@askui.com. No-pixel-coordinates note added too.

@@ -0,0 +1,144 @@
---
icon: Sparkles
title: Dreaming

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be moved to content/docs/extending. It explains the basic functionality.

The best practice should explain when to use if e.g. in case of Analyzing failures.

@philipph-askui philipph-askui Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done — split into two pages per your model:

  • content/docs/extending/dreaming.mdx — the functional explanation (moved here from best-practices; indexed in the Extending section).
  • content/docs/best-practices/dreaming.mdx — a new short "When to use Dreaming" page: reach for it when the same rule keeps coming up / for repeatedly-run suites / as the maintenance loop after analyzing failures; leave it off for brand-new suites or external (environment/SDK) failures. It cross-links to the Extending page.

Both section meta.json files updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants