Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Plugin returns "not logged in" when Claude CLI is logged in via bedrock

Open
  • Is something wrong?
#189 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, lua, neovim
Domain
authentication, cloud, devtools

Research direction

Start with the plugin's Claude CLI authentication handling, using the .claude/settings.json Bedrock configuration and CLAUDE_CODE_USE_BEDROCK=1 command as the reproduction case. Confirm that Claude works in the terminal but claudecode.nvim reports “Not logged in”; done means the plugin recognizes the Bedrock-authenticated session automatically.

Written by the indexing model from the issue text.

Description

Bug Description

Claude CLI works locally with Bedrock authentication, but claudecode.nvim does not.

To Reproduce

Steps to reproduce the behavior:

Standard bedrock setup:

.claude/settings.json:

{
  "awsAuthRefresh": "aws sso login --profile aws-profile-name",
  "env": {
    "AWS_PROFILE": "aws-profile-name",
    "AWS_REGION": "eu-central-1"
  },
}

Run Claude with CLAUDE_CODE_USE_BEDROCK=1

Result:

claude in terminal works fine.

claudecode.nvim isn't logged in.

Expected Behavior

Neovim plugin realises Claude is logged in automatically.

Environment

  • Neovim version: [e.g. 0.9.2] 0.11.4
  • Claude Code CLI version: [e.g. 1.0.0] 2.1.38
  • OS: [e.g. macOS 14.1] 15.7.3
  • Plugin version: [e.g. 0.1.0]

Error Messages

If applicable, add error messages or logs.

Not logged in . Run /login

Additional Context

Dominant language
Lua
Stars
3.1k
Forks
219
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No 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 coder/claudecode.nvim

All issues in coder/claudecode.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.