## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The Apps system gives agents governed access to external services
> - The managed OAuth callback discovers provider tools before it
activates a grant
> - Fresh managed connections kept every discovered tool in quarantine
> - The Apps page also counted disabled tools as available actions
> - This pull request makes setup activation atomic and keeps later
catalog changes quarantined
> - The benefit is a usable catalog after consent without weakening
reauthorization safeguards
## Linked Issues or Issue Description
N/A — no public GitHub issue exists for this follow-up. Related merged
work:
[#12619](https://github.com/paperclipai/paperclip/pull/12619) and
[paperclip-cloud
#319](https://github.com/paperclipai/paperclip-cloud/pull/319).
**What happened?**
A fresh Paperclip-managed OAuth connection discovered the correct Google
Workspace tools, but it left every allowed tool in quarantine. The Apps
page then reported zero actions for write profiles and counted disabled
actions for read profiles.
**Expected behavior**
A fresh or revived managed connection must remain disabled until
Paperclip stores credentials, discovers the catalog, reviews the profile
allowlist, installs default policies, and activates the connection. A
later reauthorization must preserve user choices. A later catalog change
must quarantine new or changed tools.
**Steps to reproduce**
1. Connect a managed Google Workspace write profile.
2. Complete provider consent and return through the instance callback.
3. Open the connection in Apps.
4. Observe that the connection is active but the allowed actions remain
quarantined.
**Paperclip version or commit**
Commit `c7ebc089c` from merged pull request #12619.
**Deployment mode**
Self-hosted local development through Tailscale HTTPS. The same callback
logic applies to Cloud-hosted instances.
**Installation method**
Built from source with pnpm.
**Agent adapter(s) involved**
Not adapter-specific. This change affects the core Apps and tool-access
paths.
## What Changed
- Kept fresh and revived managed connections in the draft state until
catalog finalization succeeds.
- Added a managed-draft refresh option that quarantines discovery
results without changing generic draft behavior.
- Activated reviewed profile tools, created bindings, and installed
ask-first policies in the existing finalization transaction.
- Preserved custom profiles, bindings, archived state, and policies
during ordinary reauthorization.
- Kept new or changed tools quarantined after activation and kept
out-of-profile tools disabled.
- Counted only active catalog entries as available actions in the Apps
page.
- Added retry, revival, reauthorization, policy, profile, and UI
regression coverage.
## Verification
- `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/tool-access-service.test.ts` — passed, 208 tests.
- `pnpm --filter @paperclipai/ui exec vitest run
src/pages/apps/AppDetail.test.tsx` — passed, 52 tests.
- Server and UI typechecks passed.
- `pnpm build` — passed on the final tree.
- `pnpm check:token-gates` — passed.
- `git diff --check` — passed.
- Browser walkthrough — passed for all 16 enabled Google Workspace
profiles through the staging Cloud broker and a self-hosted Tailscale
HTTPS instance. Every final connection became active and exposed at
least one allowed action.
- `pnpm test:run` — the changed suites passed. The shared live-QA
environment caused unrelated workspace-runtime concurrency and cleanup
failures, so hosted CI is the clean-environment authority for the full
suite.
## Risks
- The change affects managed OAuth only. Customer-owned OAuth setup
keeps its current behavior.
- A failed initial finalization now leaves a safe draft that the
callback can retry.
- An ordinary active reauthorization does not rebuild defaults, so
existing user policy remains intact.
- There are no database migrations and no public API changes.
> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.
## Model Used
- OpenAI Codex, GPT-5.6, with reasoning, repository tools, browser
control, code execution, test execution, and parallel subagent review.
The effective context window was managed by the Codex task runtime.
## Checklist
- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and the changed suites pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
0b73ebb86c