8000 feat(circles): circles of trust and sharing with them, with API and MCP by adeelahmad · Pull Request #626 · adeelahmad/lense · GitHub
[go: up one dir, main page]

Skip to content

feat(circles): circles of trust and sharing with them, with API and MCP - #626

Merged
adeelahmad merged 12 commits into
mainfrom
claude/project-thread-97gkhw
Oct 18, 2026
Merged

adeelahmad merged 12 commits into
mainfrom
claude/project-thread-97gkhw

Conversation

@adeelahmad
Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: there was no way to tell Lens who your family is, or to pass something from your timeline to them.

After: you put people you already share a namespace with into circles of your own (Immediate family, Close family, Friends, Colleagues are suggested) and share an activity or a resource with a circle and a note. Each person gets share.received in their own timeline (their automations can follow it) and you get share.sent. With the item also grants permission on that one resource (needs publish). Undo takes the share back everywhere, with the permissions it gave. Nothing in a vault can be shared.

How: app/domain/circles.py stores circle, circle_share and circle_share_to rows and registers two event sources (shares_sent, shares_received), each paging only the viewer's own rows. Routes under /api/v1/circles; MCP tools list_circles, save_circle, share_with_circle, undo_share; the assistant asks before sharing.

This is the first of six stacked PRs for the agent family network (web app, sharing rules, when-free, ask their agent, and ActivityPub follow).

Motivation and Context

The agent family network thread: agents grounded in each person's data, sharing only within the family.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests.
  • My change requires documentation updates, and I have updated docs/ accordingly.
  • Users need more than the title to understand it, so I wrote it in changelog.d/circles.md.

Done questions (AGENTS.md)

  • Goal: merges on green CI (pending); the web app and the rest follow in the next PRs.
  • Agents: API, MCP tools and the assistant.
  • Zero setup: no new prerequisite; tables are created with IF NOT EXISTS.
  • Fewest clicks: n/a in this PR, since the web UI comes in the next one.
  • Configurable: n/a, no new settings.
  • Light: no new dependency or service.
  • Private and secure: circles are private to their owner and hold only people you already share with; threat model P-CIRCLES added.
  • Cost: no model calls.
  • User decides: the assistant asks before sharing; nothing is shared on its own; defaults unchanged.
  • Upgrades: new tables only, so no existing data changes.
  • Honest: README lists it as built, and the rest of the circles work as planned.
  • Tests (tests/api/test_circles.py, MCP tests), docs (docs/circles.md, api, mcp, automations), and openapi/client regenerated with make openapi.
  • Open standards: activities are AS2-shaped l 8000 ike the rest of the timeline; no new dependency.
  • Reported in the project thread; refine-later items are in docs/circles.md.
  • Reuse: builds on events, permissions and the MCP toolbox.

Generated by Claude Code

claude added 12 commits October 18, 2026 06:20
Put the people close to you in circles and share an activity or a resource
with a circle and a note: each person gets share.received in their own
timeline, the sharer gets share.sent. With the item gives permission on that
one resource (needs publish); undo takes it all back. Vaults never share.
API under /api/v1/circles, MCP tools and the assistant's tools, which ask first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
…h share links

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
…the merge

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012v8sNShSVTXxoPDab62A1L
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0