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

[PR #270] [MERGED] docs: clarify current web settings coverage #284

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

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/270
Author: @mason5052
Created: 4/16/2026
Status: ✅ Merged
Merged: 4/23/2026
Merged by: @asdek

Base: feature/next-release ← Head: codex/issue-191-settings-coverage

📝 Commits (2)

  • e86052b docs: clarify current web settings coverage
  • aa718e2 docs: clarify settings config paths

📊 Changes

2 files changed (+40 additions, -0 deletions)

View changed files

📝 README.md (+18 -0)
📝 backend/docs/config.md (+22 -0)

📄 Description

Summary

  • clarify which settings areas are already managed in the web UI
  • document which configuration still lives in environment variables, compose files, or mounted config files

Problem

Issue #191 asks for configuration from the web console, but the current docs do not clearly separate shipped web settings from configuration that is still server-managed.

That makes it easy to overestimate current UI coverage, especially around search providers, third-party integrations, and LLM credentials or endpoint settings.

Solution

  • add a short Current Web Settings Coverage section to README.md
  • add a matching clarification near the top of backend/docs/config.md
  • explicitly distinguish provider profiles, prompts, and API tokens from server-managed credentials, search providers, third-party integrations, and MCP server setup

User Impact

Users get a more accurate picture of what can already be configured after startup and what still has to be configured on the server.

This also makes #191 easier to treat as a follow-up on the remaining gap instead of a blind reimplementation of features that already exist.

Test Plan

  • re-checked each capability claim against the current frontend settings pages, GraphQL schema and resolvers, and config package
  • ran git diff --check

References #191.

🔄 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/270 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/16/2026 **Status:** ✅ Merged **Merged:** 4/23/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-191-settings-coverage` --- ### 📝 Commits (2) - [`e86052b`](https://github.com/vxcontrol/pentagi/commit/e86052b041b0b3b8d81cf386ff66360258c24f3f) docs: clarify current web settings coverage - [`aa718e2`](https://github.com/vxcontrol/pentagi/commit/aa718e23305b8495389b43cc8125b86d36121aa0) docs: clarify settings config paths ### 📊 Changes **2 files changed** (+40 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+18 -0) 📝 `backend/docs/config.md` (+22 -0) </details> ### 📄 Description ## Summary - clarify which settings areas are already managed in the web UI - document which configuration still lives in environment variables, compose files, or mounted config files ## Problem Issue #191 asks for configuration from the web console, but the current docs do not clearly separate shipped web settings from configuration that is still server-managed. That makes it easy to overestimate current UI coverage, especially around search providers, third-party integrations, and LLM credentials or endpoint settings. ## Solution - add a short `Current Web Settings Coverage` section to `README.md` - add a matching clarification near the top of `backend/docs/config.md` - explicitly distinguish provider profiles, prompts, and API tokens from server-managed credentials, search providers, third-party integrations, and MCP server setup ## User Impact Users get a more accurate picture of what can already be configured after startup and what still has to be configured on the server. This also makes #191 easier to treat as a follow-up on the remaining gap instead of a blind reimplementation of features that already exist. ## Test Plan - re-checked each capability claim against the current frontend settings pages, GraphQL schema and resolvers, and config package - ran `git diff --check` References #191. --- <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:02 -04:00
yindo closed this issue 2026-06-06 22:10:03 -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#284
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?