Paperclip
Paperclip lets model discovery use company secrets
Paperclip proposes letting model discovery resolve company-scoped secrets, while archived-company URLs gain an explicit recovery path and agent hiring is blocked when the selected adapter cannot run. The cluster connects configuration visibility, lifecycle state and executable capability.
paperclipai/paperclip PR #11308 is the inspected primary source: “feat(adapters): let model discovery see company secrets.” The related records below were inspected as supporting context rather than independent confirmation.
The facts
- paperclipai/paperclip PR #11308 was created 2026-08-13T00:17:26Z and was open at inspection; its title is “feat(adapters): let model discovery see company secrets.” - paperclipai/paperclip PR #11302 was created 2026-08-12T23:35:47Z and was open at inspection; its title is “feat(ui): bounce cold arrivals off archived company URLs, add Unarchive.” - paperclipai/paperclip PR #10256 was created 2026-07-25T15:51:01Z and was closed at inspection; its title is “fix(agents): refuse to hire onto an adapter this instance cannot run.” - The repository reported 77738 stars, 5069 open issues, default branch master, and last push 2026-08-13T00:06:24Z. - The latest tagged-release baseline checked was v2026.722.0 published 2026-07-22T23:05:41Z.
What changed
paperclipai/paperclip PR #11308 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - Paperclip stores provider API keys as per-company secrets and injects them when an agent runs - Adapter model discovery starts the provider CLI, which lists only the providers it can authenticate - listModels accepts no arguments, so discovery sees only the server process environment - A key held as a company secret therefore never shows a model in the picker - This pull request adds an optional, already-resolved environment to model discovery - The benefit is that secret-backed providers show their models without hardcoded on-disk configuration Linked Issues or Issue Description Refs #10919 — my earlier PR on the same root cause. That PR makes a failed model check non-fatal. This PR makes the discovery itself succeed. The two are complementary: keep the fallback for residual failures, and remove the most common cause of them. Refs #11169 — also touches adapter model discovery, for OpenCode. No overlap in the files changed. No public issue covers this. The
paperclipai/paperclip PR #11302 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - Archiving a company hides it from the sidebar switcher, but remembered last-visited paths, browser history, bookmarks, and restored tabs keep depositing users onto its URLs long after archiving - Since the selection ping-pong fix (#11300) those arrivals render, but the user is stranded inside a workspace the sidebar refuses to show — and unarchiving had no UI anywhere, so the only way back was a hand-typed settings URL - This pull request bounces cold arrivals at archived company URLs to an active company (with a toast naming why), lets deliberate visits stick, and adds an Unarchive action to the companies list - The benefit is that stale URLs stop stranding users in retired workspaces, and archived companies become restorable from the one page that still lists them Linked Issues or Issue Description Follow-up to #11300. No existing issue for the remaining gap; description follows the enhancement template: What happened?** After #11300, opening an archived company's URL (stale
paperclipai/paperclip PR #10256 reports: Thinking Path - Paperclip is the open source app people use to manage AI agents for work - Hiring an agent means choosing a harness (adapter) for it, and an instance can declare which harnesses it actually runs through PAPERCLIP_ADAPTERS, which reconcileAdapterAvailability turns into a disabled set at boot - The hire and create routes validate the adapter type with assertKnownAdapterType, which only asks whether the adapter is REGISTERED — a disabled adapter passes - So an agent can be created on a harness the instance cannot run, and the failure only appears later, per run, at lease time: Adapter "..." is not in the configured adapter registry - By then the error is in a run log, minutes after the choice, with nothing tying it back to the harness the user picked; the agent also keeps accepting work it can never do - This pull request validates the hire and create paths against the ENABLED set and refuses with a message that names the adapters that are available - The benefit is that an
Why it matters
A model picker that cannot see the credentials the runtime will use gives false negatives; a hiring flow that accepts an unrunnable adapter gives false positives. Both are control-plane lies. The operator test is whether visible output, retained state and authority still describe the same event after retries, background work or restart.
Current
The primary record was open when captured on 2026-08-13. The tagged-release baseline was v2026.722.0 published 2026-07-22T23:05:41Z. Repository metadata, full source bodies, current pull requests and issues, releases, Google News, Hacker News, Lobsters, Metamesh and the rendered ClawCharts row were inspected. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/paperclipai/paperclip/pull/11308. Supporting records are https://github.com/paperclipai/paperclip/pull/11302 and https://github.com/paperclipai/paperclip/pull/10256. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts and reproductions remain attributed to their authors unless identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Resolve secrets only in the scoped discovery path, record which adapter actually passed capability checks, and keep archived organizations from silently accepting new work. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.