Jbcontext requires login manually every day
@Elizaveta239 is already working on this.
Since Oct 13, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- shell
- Domain
- authentication
Research direction
Start by reproducing the daily login requirement in jbcontext and tracing its current authentication flow. Determine how OAuth access and refresh tokens should be stored and renewed, and verify that a missed login no longer causes a tool call to fail permanently. No file or test is named in the issue.
Written by the indexing model from the issue text.
Description
Hi,
I've made a custom tool for my harness, utilizing jbcontext.
The issue I'm having is that it requires me to login literally every day, if i will forget to login model will fail tool call once and will never recover.
Can there be some kind of oAuth implemented with proper auth tokens and refresh tokens?
- Dominant language
- Shell
- Stars
- 38
- Forks
- 4
- Avg merge
- 5h 26m
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from JetBrains/context
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Marketplace Configuration File is missingPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
code_search (MCP): absolute pathFilter to another indexed checkout is silently ignored and returns results from the root repositoryMay be free again @Elizaveta239 claimed this 34 days ago, and no pull request is open. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in JetBrains/context
Similar issues
-
[Config] Neo Coolcam NAS-WS01Z (0x0258:0x0003:0x1085): param 2 "Alarm Interval" is 1 byte, not 2Open
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pearu/agent-sandbox#412 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ScoopInstaller/Nonportable#665 ·
-
bot-found documentation priority: P3
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
madenvel/KalinkaPlayer#602 ·