vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 12:37:04 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #193] [Enhancement]: File uploads for Flows #76

New Issue
Open
opened 2026-06-06 22:08:59 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:08:59 -04:00
Owner
Copy Link
Copy Source

Originally created by @ThatServerGuy on GitHub (Mar 11, 2026).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/193

Originally assigned to: @asdek on GitHub.

Target Component

Core Services (Frontend UI/Backend API)

Enhancement Description

Add file upload support scoped to individual workflows, with files stored in a shared location accessible by everything the workflow spawns — the Assistant, Automation, and the container.
Requirements:
∙ Upload interface added to the workflow UI
∙ Shared storage mounted and accessible across all spawned functions (Assistant, Automation, Docker container)
∙ Files isolated and scoped to their parent workflow
∙ On workflow deletion, prompt user to archive or permanently delete associated files before removal is completed​​​​​​​​​​​​​​​​

Technical Details

No response

Designs and Mockups

No response

Alternative Solutions

No response

Verification

  • I have checked that this enhancement hasn't been already proposed
  • This enhancement aligns with PentAGI's goal of autonomous penetration testing
  • I have considered the security implications of this enhancement
  • I have provided clear use cases and benefits
Originally created by @ThatServerGuy on GitHub (Mar 11, 2026). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/193 Originally assigned to: @asdek on GitHub. ### Target Component Core Services (Frontend UI/Backend API) ### Enhancement Description Add file upload support scoped to individual workflows, with files stored in a shared location accessible by everything the workflow spawns — the Assistant, Automation, and the container. Requirements: ∙ Upload interface added to the workflow UI ∙ Shared storage mounted and accessible across all spawned functions (Assistant, Automation, Docker container) ∙ Files isolated and scoped to their parent workflow ∙ On workflow deletion, prompt user to archive or permanently delete associated files before removal is completed​​​​​​​​​​​​​​​​ ### Technical Details _No response_ ### Designs and Mockups _No response_ ### Alternative Solutions _No response_ ### Verification - [x] I have checked that this enhancement hasn't been already proposed - [x] This enhancement aligns with PentAGI's goal of autonomous penetration testing - [x] I have considered the security implications of this enhancement - [x] I have provided clear use cases and benefits
yindo added the enhancement label 2026-06-06 22:08:59 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#76
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?