yashdev9274 / yashdev9274/supercli
ECONNREFUSED Prisma error when checking subscription, CLI always reports "You don't have an active subscription"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 214
- Forks
- 41
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 34
Description
Hi team,
I'm experiencing an issue when using the latest version of the Supercode CLI.
After starting the CLI, it fails while checking my subscription and prints the following error:
[subscription-check] DB error: PrismaClientKnownRequestError
code: 'ECONNREFUSED'
meta: { modelName: 'Subscription' }
clientVersion: '7.8.0'
You don't have an active subscription. Run /upgrade to subscribe to Spark Premium ($1/mo) and start using the CLI.
Environment
OS: macOS
Node.js: v22.17.1
npm: 10.9.2
Supercode CLI: latest (installed via npm install -g supercode-cli@latest)
What I expected
The CLI should either:
successfully validate my subscription, or
display a clear authentication/subscription error if there is an issue with my account.
What happened
Instead, the CLI throws a Prisma ECONNREFUSED error during subscription.findFirst() and then reports that I don't have an active subscription.
Questions
Is this a known issue?
Does the CLI require Node.js 24? I noticed an EBADENGINE warning during installation because one dependency requires Node >= 24.
Is this a client-side issue, or is the subscription service/database currently unavailable?
Is there anything I can do to troubleshoot or work around this problem?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the subscription check in the Supercode CLI and inspect the subscription.findFirst() path that reports PrismaClientKnownRequestError with ECONNREFUSED. Use the reported Node.js and CLI versions to compare the runtime requirements, then verify that connection failures produce a clear subscription error rather than the inactive-subscription message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend, cli, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100