1jehuang / 1jehuang/jcode

Tried for hours: UNUSABLE - Unstable Provider Setup, Broken Model Management, and Concerning Telemetry Collection

Open
#177 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: medium question triage: unclear
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

I really want to see JCode succeed because I think the overall direction is promising. I’ve spent several hours trying to set it up on macOS and gave it multiple chances, but the current experience has been extremely frustrating, especially around providers and models.

I consistently ran into issues where providers could not be configured properly, models were unavailable, switching models did not work, and even the default provider/models frequently failed. Sometimes the app works, but most of the time it feels unreliable and unpredictable.

There are also some concerning behaviors around permissions and telemetry. In a few cases, actions happened without clear confirmation prompts, including file/folder modifications. The amount of telemetry being collected also feels excessive and should be communicated more transparently.

I’m sharing this because I genuinely think the project has potential, but the basics need to be stable first. Provider setup, model management, reliability, permissions, and configuration UX all need significant improvement. Right now, the experience feels very unfinished, and it would help to be more transparent about what is currently stable versus experimental.

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.

Research direction

No files, tests, or entry points are identified. Start by reproducing provider and model setup on macOS, then inspect the relevant configuration, permission, and telemetry paths. Done requires reliable provider and model selection, clear confirmation for file or folder changes, and transparent telemetry communication.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
ai, cli, observability, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.