You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(node:2610641) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
TypeError: json.map is not a function
at Claude.getConversations (file:///home/keinvanity/.local/lib/node_modules/claude-cli/node_modules/claude-ai/index.js:298:21)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Claude.init (file:///home/keinvanity/.local/lib/node_modules/claude-cli/node_modules/claud
e-ai/index.js:174:37)
at async main (file:///home/keinvanity/.local/lib/node_modules/claude-cli/index.js:124:5)
and running via the library raises another error
file:///home/keinvanity/Downloads/claude-misc/Explosion-Scratch-claude-unofficial-api/node_modules/claude-ai/index.js:171
throw new Error(JSON.stringify(organizations, null, 2))
^
Error: {
"error": {
"message": "We are unable to serve your request",
"type": "permission_error"
}
}
at Claude.init (file:///home/keinvanity/Downloads/claude-misc/Explosion-Scratch-claude-unofficial-api/node_modules/claude-ai/index.js:171:19)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async file:///home/keinvanity/Downloads/claude-misc/Explosion-Scratch-claude-unofficial-api/main.js:7:1
Node.js v22.9.0
The text was updated successfully, but these errors were encountered:
This particular problem can be fixed adding user-agent to the headers everywhere.
After it I can login and e.g. export my existing conversations.
But still it fails on creating new conversation with 403 error ("We are unable to serve your request").
I have no idea why. Because I can do the same with barebone curl without any problem.
running
claude --key
raises the following errorand running via the library raises another error
The text was updated successfully, but these errors were encountered: