feat: persist agents & strategies in Postgres#134
Draft
FlyM1ss wants to merge 5 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE — implementation in progress (2 of 9 tasks landed). Opened early, as a draft, because CI only runs on a PR and this branch's whole point is exercising the live-Postgres tier on every push. This line goes when the branch is complete.
Optional Postgres backends for
external_agents,agent_versions, andstrategies, selected byCONTENT_DATABASE_URL, cloning the shippedUSERS_DATABASE_URLusers fix. Without them every registered agent and issued API key dies on each Render deploy (free tier, no disk) — andresolve_api_key()is the sole auth path for/api/v1and/api/v2.docs/superpowers/specs/2026-07-15-agent-strategy-persistence-design.mddocs/superpowers/plans/2026-07-15-agent-strategy-persistence.mdThe plan's original gate ("DO NOT MERGE until
CONTENT_DATABASE_URLis set in Render") is already discharged — the var is set on the prod service, so the correct rollout order (env var first, then merge) is satisfied. The gate above is the real one: the work isn't finished yet.