[PR #292] [MERGED] docs: explain assistant flow management for active flows #301

New Issue

2026-06-06T22:10:07-04:00

yindo commented

2026-06-06 22:10:07 -04:00

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/292
Author: @mason5052
Created: 4/28/2026
Status: ✅ Merged
Merged: 4/30/2026
Merged by: @asdek

Base: feature/next-release ← Head: codex/issue-192-assistant-flow-management-docs

📝 Commits (1)

9666cf3 docs: explain assistant flow management

📊 Changes

1 file changed (+9 additions, -0 deletions)

View changed files

📝 README.md (+9 -0)

📄 Description

Summary

document how the Assistant view can manage an active flow without restarting the automation
explain the explicit control path for checking status, stopping work, submitting follow-up input, and patching planned subtasks
keep the guidance in the README first-use section where users are most likely to look for this workflow

Problem

Issue #192 shows that users want a safe way to influence an in-progress automation. The implementation direction has shifted away from an in-memory queue and toward explicit assistant-side flow management tools, but that workflow is still hard to discover from the main README.

Solution

Add a short user-facing section to the first-use guide that explains when to open the Assistant view for the same flow and what kinds of changes it is appropriate to make there.

User Impact

Users get a clearer path for steering an active flow without assuming PentAGI uses a hidden background queue. This should reduce confusion around how to redirect or clarify an automation run after it has already started.

Test Plan

verify the new README section matches the current assistant flow-management behavior documented in backend/docs/flow_execution.md
verify the wording does not promise hidden queueing or direct mid-command interruption
git diff --check

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/292 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/28/2026 **Status:** ✅ Merged **Merged:** 4/30/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-192-assistant-flow-management-docs` --- ### 📝 Commits (1) - [`9666cf3`](https://github.com/vxcontrol/pentagi/commit/9666cf35ca143ed0bdb8fd16e7e10d61a17c07c0) docs: explain assistant flow management ### 📊 Changes **1 file changed** (+9 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+9 -0) </details> ### 📄 Description ## Summary - document how the Assistant view can manage an active flow without restarting the automation - explain the explicit control path for checking status, stopping work, submitting follow-up input, and patching planned subtasks - keep the guidance in the README first-use section where users are most likely to look for this workflow ## Problem Issue #192 shows that users want a safe way to influence an in-progress automation. The implementation direction has shifted away from an in-memory queue and toward explicit assistant-side flow management tools, but that workflow is still hard to discover from the main README. ## Solution Add a short user-facing section to the first-use guide that explains when to open the Assistant view for the same flow and what kinds of changes it is appropriate to make there. ## User Impact Users get a clearer path for steering an active flow without assuming PentAGI uses a hidden background queue. This should reduce confusion around how to redirect or clarify an automation run after it has already started. ## Test Plan - verify the new README section matches the current assistant flow-management behavior documented in `backend/docs/flow_execution.md` - verify the wording does not promise hidden queueing or direct mid-command interruption - `git diff --check` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-06-06 22:10:07 -04:00

yindo closed this issue

2026-06-06 22:10:07 -04:00

yindo referenced this issue

2026-06-06 22:10:08 -04:00

[PR #301] [MERGED] fix: apply custom prompts to new sessions #306

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#301