[BUG] Windows: Chat never responds after successful login (Prisma performIO error)

Open
#243 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
postgresql, typescript
Domain
backend, cli, databases, operating-systems

Research direction

Start by reproducing the issue on Windows 10 with Supercode CLI v0.1.90 and inspect the Prisma session lookup shown in the logs. Trace the PostgreSQL adapter's performIO failure before model requests are sent; done means a prompt receives an assistant response without the session lookup error.

Written by the indexing model from the issue text.

Description

bug

Environment

  • OS: Windows 10 Pro (10.0.19045.6466)
  • Supercode CLI: v0.1.90
  • Authentication: GitHub login succeeds
  • Models tested:
    • GLM 5.2
    • GLM 5.1
    • DeepSeek V4 Flash
    • Kimi K2.6

Problem

Authentication completes successfully and I can switch between models.

However, after typing any prompt (e.g. hi), Supercode never returns a response.

The UI shows:

you > hi
Worked for 1.3s

but no assistant message is ever displayed.

Debug Logs

prisma.session.findUnique({
where: {
token: "..."
},
select: {
userId: true
}
})

prisma:driver-adapter:pg Error in performIO: {}

prisma:client:request_handler {}

The CLI appears to fail while reading the session from PostgreSQL before any request is sent to the selected model.

Expected

The assistant should respond to the prompt.

Actual

The prompt is accepted, but no response is generated and the session lookup fails.

Dominant language
TypeScript
Stars
214
Forks
41
Avg merge
2h 26m
Merged PRs (30d)
34

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yashdev9274/supercli

All issues in yashdev9274/supercli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.