Add worker management UI, logic, and REST endpoints #206

Merged

rwachters merged 2 commits from add-worker-management into change-mcp-tool-call-architecture

2026-04-30 02:37:11 +00:00

rwachters commented

2026-04-30 02:35:53 +00:00

(Migrated from github.com)

Summary

This pull request introduces a comprehensive worker management feature, including new UI components, backend logic, and API endpoints. Key changes include:

UI Enhancements: Added a new "Workers" tab in the settings for managing registered workers, including functionalities for viewing, editing, and deleting worker details.
ViewModel: Implemented WorkersViewModel for worker list and operations management.
Repository Updates: Extended WorkerRepository and WorkerApi to support worker update and deletion.
API Endpoints:
- PATCH /api/v1/workers/{id}: Enables worker updates (e.g., display name and allowed scopes).
- DELETE /api/v1/workers/{id}: Allows worker deletions with ownership checks.
Integration Tests: Comprehensive tests ensure proper verification of ownership, not-found scenarios, and end-to-end API functionalities.

Checklist

Code functionality matches requirements.
Tests added or updated as applicable.
Documentation is updated where necessary.
Code is linted and follows style guidelines.

### Summary This pull request introduces a comprehensive worker management feature, including new UI components, backend logic, and API endpoints. Key changes include: - **UI Enhancements**: Added a new "Workers" tab in the settings for managing registered workers, including functionalities for viewing, editing, and deleting worker details. - **ViewModel**: Implemented `WorkersViewModel` for worker list and operations management. - **Repository Updates**: Extended `WorkerRepository` and `WorkerApi` to support worker update and deletion. - **API Endpoints**: - `PATCH /api/v1/workers/{id}`: Enables worker updates (e.g., display name and allowed scopes). - `DELETE /api/v1/workers/{id}`: Allows worker deletions with ownership checks. - **Integration Tests**: Comprehensive tests ensure proper verification of ownership, not-found scenarios, and end-to-end API functionalities. ### Checklist - [ ] Code functionality matches requirements. - [ ] Tests added or updated as applicable. - [ ] Documentation is updated where necessary. - [ ] Code is linted and follows style guidelines.

Rows
Columns