feat(client): add remote project support #338

Closed
opened 2026-02-22 23:41:24 +00:00 by freemo · 7 comments
Owner

Metadata

  • Commit Message: feat(client): add remote project support
  • Branch: feature/m7-post-server

Background

Remote resource selection and server execution request wiring enable multi-server project management. Project-name resolution handles remote namespaces and server aliases. CLI scaffolding for --remote flags is added.

Acceptance Criteria

  • Add remote resource selection and server execution request wiring.
  • Add project-name resolution rules for remote namespaces and server aliases.
  • Add agents project list --remote and plan use --remote scaffolding (server-only).
  • Add explicit error when remote project is not found or user lacks access.
  • Add remote project caching with TTL to minimize repeated server calls.

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Add remote resource selection and server execution request wiring.
  • Add project-name resolution rules for remote namespaces and server aliases.
  • Add agents project list --remote and plan use --remote scaffolding (server-only).
  • Add explicit error when remote project is not found or user lacks access.
  • Add remote project caching with TTL to minimize repeated server calls.
  • Add CLI output for remote project list (namespace, id, last_updated).
  • Add docs/reference/server_remote_projects.md with project selection semantics.
  • Add examples for project list --remote and plan use --remote.
  • Tests (Behave): Add scenarios for remote project selection errors.
  • Tests (Robot): Add remote execution mock tests.
  • Tests (ASV): Add benchmarks/server_remote_project_bench.py for request overhead baseline.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: ### Section 18: Deferred Work
Status: Open

## Metadata - **Commit Message**: `feat(client): add remote project support` - **Branch**: `feature/m7-post-server` ## Background Remote resource selection and server execution request wiring enable multi-server project management. Project-name resolution handles remote namespaces and server aliases. CLI scaffolding for `--remote` flags is added. ## Acceptance Criteria - [ ] Add remote resource selection and server execution request wiring. - [ ] Add project-name resolution rules for remote namespaces and server aliases. - [ ] Add `agents project list --remote` and `plan use --remote` scaffolding (server-only). - [ ] Add explicit error when remote project is not found or user lacks access. - [ ] Add remote project caching with TTL to minimize repeated server calls. ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Add remote resource selection and server execution request wiring. - [ ] Add project-name resolution rules for remote namespaces and server aliases. - [ ] Add `agents project list --remote` and `plan use --remote` scaffolding (server-only). - [ ] Add explicit error when remote project is not found or user lacks access. - [ ] Add remote project caching with TTL to minimize repeated server calls. - [ ] Add CLI output for remote project list (namespace, id, last_updated). - [ ] Add `docs/reference/server_remote_projects.md` with project selection semantics. - [ ] Add examples for `project list --remote` and `plan use --remote`. - [ ] Tests (Behave): Add scenarios for remote project selection errors. - [ ] Tests (Robot): Add remote execution mock tests. - [ ] Tests (ASV): Add `benchmarks/server_remote_project_bench.py` for request overhead baseline. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: ### Section 18: Deferred Work **Status**: Open
freemo added this to the (deleted) milestone 2026-02-22 23:41:24 +00:00
freemo modified the milestone from (deleted) to v3.6.0 2026-02-23 00:07:05 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 51 / 2026-03-31 (previously Day 46 / 2026-03-26)

**Expected completion updated (Day 15 rebaseline):** Day 51 / 2026-03-31 (previously Day 46 / 2026-03-26)
freemo added the due date 2026-03-18 2026-02-23 18:42:01 +00:00
freemo self-assigned this 2026-02-24 21:53:38 +00:00
Author
Owner

Starting implementation of remote project support.

Plan:

  • Create src/cleveragents/client/remote_project.py with RemoteProjectClient
  • Remote resource selection and server execution request wiring
  • Project-name resolution for remote namespaces and server aliases
  • Remote project caching with TTL
  • Error handling for missing/inaccessible remote projects
  • Behave, robot, and benchmark tests
Starting implementation of remote project support. Plan: - Create `src/cleveragents/client/remote_project.py` with RemoteProjectClient - Remote resource selection and server execution request wiring - Project-name resolution for remote namespaces and server aliases - Remote project caching with TTL - Error handling for missing/inaccessible remote projects - Behave, robot, and benchmark tests
Author
Owner

PM Acknowledgment (Day 31):

Thank you @freemo. PR submitted and tracked.

Status: All server/UI PRs have merge conflicts against current develop (17 PRs merged Days 30-31). Please rebase when ready for review.

Priority: M6 work — continue at current pace. Your velocity is strong (5 merges Day 30).

**PM Acknowledgment (Day 31)**: Thank you @freemo. PR submitted and tracked. **Status**: All server/UI PRs have merge conflicts against current develop (17 PRs merged Days 30-31). Please rebase when ready for review. **Priority**: M6 work — continue at current pace. Your velocity is strong (5 merges Day 30).
Author
Owner

Implementation complete in commit d5cfd33cc5 on branch feature/m7-post-server. PR #1111 submitted for review.

All subtasks addressed:

  • Remote resource selection and execution wiring
  • Project-name resolution for namespaces and aliases
  • TTL-based project cache with invalidation
  • Explicit errors for not-found/access-denied
  • Reference documentation
  • Behave scenarios (16 scenarios)
  • Robot Framework smoke tests
  • ASV benchmark
Implementation complete in commit d5cfd33cc5715e1cd029ef9a628dec5d79952572 on branch `feature/m7-post-server`. PR #1111 submitted for review. All subtasks addressed: - [x] Remote resource selection and execution wiring - [x] Project-name resolution for namespaces and aliases - [x] TTL-based project cache with invalidation - [x] Explicit errors for not-found/access-denied - [x] Reference documentation - [x] Behave scenarios (16 scenarios) - [x] Robot Framework smoke tests - [x] ASV benchmark
freemo added reference feature/m7-post-server 2026-03-23 00:21:00 +00:00
Author
Owner

PR #1111 reviewed — changes requested. Three blocking issues remain: (1) merge conflicts with master, (2) two files exceed the 500-line limit, and (3) unclean commit history. See PR #1111 review comment for full details.


Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

PR #1111 reviewed — **changes requested**. Three blocking issues remain: (1) merge conflicts with master, (2) two files exceed the 500-line limit, and (3) unclean commit history. See [PR #1111 review comment](https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/1111#issuecomment-81158) for full details. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
Author
Owner

PR #1111 has been merged successfully. Issue should now be resolved.


Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

PR #1111 has been merged successfully. Issue should now be resolved. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
Author
Owner

PR #1111 has been reviewed and changes requested. Three blocking issues remain (merge conflicts, 2 files over 500-line limit, unclean commit history). The code quality is excellent — once process issues are resolved, the PR is ready to merge.

See PR #1111 comment for full review.


Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

PR #1111 has been reviewed and **changes requested**. Three blocking issues remain (merge conflicts, 2 files over 500-line limit, unclean commit history). The code quality is excellent — once process issues are resolved, the PR is ready to merge. See [PR #1111 comment](https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/1111#issuecomment-109084) for full review. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-03-18

Blocks
#399 Epic: Post-MVP Server & Clients
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#338
No description provided.