BuilderIO / BuilderIO/micro-agent

Micro Agen Open AI 401 Authentication Fails (no such user)

Open
#62 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
4.3k
Forks
380
PR merge metrics
No merged PRs in 30d

Description

Hi is there some one else have same problem with me, i got this message when using micro agent it said 401 Auth Fails (no such user). looks like the key not correct

I ve been trouble shoot like
1. using micro-agent config to set key
2. create 2 open api key

but there is no luck at all, any one have answer please let me know i really appricate
Thank You

(base) clozetteid@ClozetteIDs-MacBook-Air ~ % micro-agent -version
(node:5263) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

┌ 🦾 Micro Agent

◇ What would you like to do?
│ create fast api program


✖ 401 Authentication Fails (no such user)
at APIError.generate (file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/node_modules/openai/error.mjs:44:20)
at OpenAI.makeStatusError (file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/node_modules/openai/core.mjs:268:25)
at OpenAI.makeRequest (file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/node_modules/openai/core.mjs:311:30)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getFileSuggestion (file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/dist/cli.mjs:967:22)
at async interactiveMode (file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/dist/cli.mjs:735:33)
at async file:///opt/homebrew/lib/node_modules/@builder.io/micro-agent/dist/cli.mjs:1776:11

micro-agent v0.1.4

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with the shown `micro-agent` command and configuration steps. Inspect `dist/cli.mjs` around `getFileSuggestion` and the bundled `openai` request path to determine how credentials are loaded and sent. Done means a valid configured key no longer produces the reported 401 error, with a regression test or documented reproduction where available.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
ai, authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.