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

[PR #294] [MERGED] docs: clarify web UI account setup #303

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

📋 Pull Request Information

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

Base: feature/next-release ← Head: codex/issue-289-web-ui-account-guidance

📝 Commits (1)

  • 4a8c491 docs: clarify web UI account setup

📊 Changes

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

View changed files

📝 README.md (+11 -0)

📄 Description

Summary

  • Adds a short Web UI Accounts section to the Quick Start flow.
  • Clarifies that PentAGI does not provide public self-service sign-up from the login page.
  • Documents the default local admin account, first-login password change expectation, installer reset path, and the authenticated Users REST API path for multi-user setups.

Problem
New users can see the Web UI login screen but the README only mentioned the default credentials in one line. That made it unclear whether they should sign up from the UI, use the seeded admin account, or manage additional users elsewhere.

Solution
I added a focused README note beside the Web UI access instructions, grounded in the current seeded admin account, password reset maintenance screen, and /api/v1/users/ REST API.

User Impact
First-time operators get a clearer path into the UI and a more accurate expectation for multi-user setup without implying that public registration is available.

Test Plan

  • Verified the default admin account against the initial database migration.
  • Verified the installer has a reset-admin-password maintenance flow.
  • Verified the Users REST API routes exist in the server router.
  • Ran git diff --check.

Closes #289

🔄 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/294 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/29/2026 **Status:** ✅ Merged **Merged:** 4/30/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-289-web-ui-account-guidance` --- ### 📝 Commits (1) - [`4a8c491`](https://github.com/vxcontrol/pentagi/commit/4a8c491299c70a95173c9036a74932ca4a5cc56d) docs: clarify web UI account setup ### 📊 Changes **1 file changed** (+11 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+11 -0) </details> ### 📄 Description Summary - Adds a short Web UI Accounts section to the Quick Start flow. - Clarifies that PentAGI does not provide public self-service sign-up from the login page. - Documents the default local admin account, first-login password change expectation, installer reset path, and the authenticated Users REST API path for multi-user setups. Problem New users can see the Web UI login screen but the README only mentioned the default credentials in one line. That made it unclear whether they should sign up from the UI, use the seeded admin account, or manage additional users elsewhere. Solution I added a focused README note beside the Web UI access instructions, grounded in the current seeded admin account, password reset maintenance screen, and `/api/v1/users/` REST API. User Impact First-time operators get a clearer path into the UI and a more accurate expectation for multi-user setup without implying that public registration is available. Test Plan - Verified the default admin account against the initial database migration. - Verified the installer has a reset-admin-password maintenance flow. - Verified the Users REST API routes exist in the server router. - Ran `git diff --check`. Closes #289 --- <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:08 -04:00
yindo closed this issue 2026-06-06 22:10:08 -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 pull-request
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#303
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?