wdevs/amcs
5
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Design and implement per-user tenancy #10

New Issue
Open
opened 2026-04-03 11:12:38 +00:00 by sam · 0 comments
sam commented 2026-04-03 11:12:38 +00:00
Member
Copy Link

Summary

Add a tenancy model so AMCS can safely separate data by user, tenant, or workspace instead of assuming a single shared memory space.

Why

Per-user tenancy is listed as a deferred feature in the implementation plan. It becomes important if AMCS is used by multiple users, agents, or client applications that should not share the same thought/project namespace.

Scope ideas

  • Define the tenant boundary: user, org, workspace, or account
  • Add tenant-aware schema and indexing strategy
  • Update auth context so requests resolve to a tenant
  • Ensure searches, project lookups, files, skills, and guardrails are tenant-scoped
  • Consider migration strategy for single-tenant installs
  • Document security expectations and isolation guarantees

Acceptance criteria

  • Requests are scoped to a tenant boundary
  • Data access across tenants is prevented by design
  • Core tools behave correctly in a multi-tenant environment
  • Migration and config approach is documented

Source

Deferred feature from llm/plan.md: per-user tenancy.

## Summary Add a tenancy model so AMCS can safely separate data by user, tenant, or workspace instead of assuming a single shared memory space. ## Why Per-user tenancy is listed as a deferred feature in the implementation plan. It becomes important if AMCS is used by multiple users, agents, or client applications that should not share the same thought/project namespace. ## Scope ideas - Define the tenant boundary: user, org, workspace, or account - Add tenant-aware schema and indexing strategy - Update auth context so requests resolve to a tenant - Ensure searches, project lookups, files, skills, and guardrails are tenant-scoped - Consider migration strategy for single-tenant installs - Document security expectations and isolation guarantees ## Acceptance criteria - Requests are scoped to a tenant boundary - Data access across tenants is prevented by design - Core tools behave correctly in a multi-tenant environment - Migration and config approach is documented ## Source Deferred feature from `llm/plan.md`: per-user tenancy.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#10
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?