Sloth-ninja lays the secure groundwork for a Clio connector

The first step is quiet but consequential: a protected place to hold each user's authorised link to Clio.

integrationsecurity

Clio is legal practice management software, and Sloth-ninja has added the database foundation for connecting it to Mike. There is no live connector yet. The team has deliberately left the screens and working service behind them for later pull requests.

Separate connections for Clio Manage and Clio Grow, tied to the individual user who authorised them.
Encrypted access details and renewal credentials, with expiry and permission records kept alongside them.
A saved Clio identity for showing connection status, while browser-based users are blocked from direct access.

The design also records a practical constraint: Grow's renewal credentials must be replaced whenever they are used.

So what Legal teams already using Clio should watch this fork if they want a more controlled route between matter-management data and legal AI workflows.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`af85d350`	Clio connector PR 1: user_clio_connections migration	sloth-ninja	2026-08-03	↗ GitHub
commit body Owner-authorised 03/08/2026 (allowlist entry added by the owner). Additive table: per-user encrypted OAuth tokens for Clio Manage + Grow (one row per user per product, AES-256-GCM triplets per the user_mcp_oauth_tokens precedent, rotation-safe design note), RLS enabled, browser-role grants revoked. schema.sql mirrored. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

SHA

Subject

Author

Date

af85d350

Clio connector PR 1: user_clio_connections migration

sloth-ninja

2026-08-03

↗ GitHub

commit body

Owner-authorised 03/08/2026 (allowlist entry added by the owner).
Additive table: per-user encrypted OAuth tokens for Clio Manage + Grow
(one row per user per product, AES-256-GCM triplets per the
user_mcp_oauth_tokens precedent, rotation-safe design note), RLS
enabled, browser-role grants revoked. schema.sql mirrored.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1076.md from inside the repo you want the changes in.