Repository navigation
Contributor start here: active work and available tasks #4
Description
Maintainer reconciliation — 31 October 2026
The contributor-guide work is already integrated through #70 (thanks @Krish6115). This issue is now the navigation index, not an unclaimed documentation task. Please comment before starting work so we can avoid duplicate PRs.
Merged into dev:
- fix(desktop): deduplicate account status refresh and handle power monitor resume #64: account refresh on resume, including stale-read/logout protection.
- feat(desktop): add redacted support bundle #59 via feat(desktop): integrate metadata-only support bundles #71: metadata-only support bundle. @arzvaak led the implementation; @Krish6115 and @prashilthul privacy fixtures and credit are retained. feat(desktop): add redacted diagnostics support bundle #67/fix(desktop): tighten support bundle redaction and file handling #68 are reconciled, not additional exporters to build.
- feat(desktop): add secure mobile access through BharatCode tunnels #60: secure mobile access and admission recovery. Thanks @arzvaak. Rechecked together with current dev: 206 Desktop source tests, 65 connector tests and Desktop type-checking pass.
Already owned / in review:
- @arzvaak: fix(connector): recover corrupt admission journals safely bharatcode-mobile#2; current blocker is Expo/React Native patch alignment, tracked in fix(ci): align React Native patch with the supported Expo SDK bharatcode-mobile#3. Desktop feat(desktop): add secure mobile access through BharatCode tunnels #60 is now merged; this does not publish either app.
- @Krish6115: fix(core): add sqlite migration repair path and preserve chat columns #65 database repair and feat(session): instrument time to first token across message lifecycle #66 honest timing diagnostics; latest reviews include focused reproductions.
- @Veniyan: fix(doctor): clearer auth/config diagnostics for expired or missing sessions bharatcode-cli#10; see feat(cli): port read-only doctor diagnostics to the current CLI #72 for carrying this work into the current CLI.
Available, bounded follow-ups:
- test(desktop): verify support export and resume on native Windows/macOS #73: native Windows/macOS support-export and resume acceptance, synthetic profiles only.
- fix(ci): align React Native patch with the supported Expo SDK bharatcode-mobile#3: supported Expo/React Native patch alignment.
- fix(i18n): add missing Arabic output-limit notices #74: four missing Arabic output-limit notices, preserving English source and placeholders; a focused first contribution for someone who can verify the translation.
Use dev as the base here and main in Mobile. See CONTRIBUTING.md for package commands and privacy rules. Development merges do not publish applications. No production access or real user data is needed for these tasks. Keep tests focused on changed boundaries; include exact source and reproducible commands.
Activity
prashilthul commentedon Oct 26, 2026
Hi! I'd like to contribute to this. Could you assign it to me?
Krish6115 commentedon Oct 27, 2026
Hey! Hi shrey i took a pass at CONTRIBUTING.md to bring it up to date for this repo. Replaced the outdated anomalyco/opencode links and added clear context on packages/desktop, local testing, and our auth setup in #61..
[-]Start here: contributing to BharatCode Desktop[/-][+]Contributor start here: active work and available tasks[/+]shrey16 commentedon Oct 31, 2026
One additional good first issue is now available: #74, four missing Arabic output-limit notices. Reproduced independently on current dev; no feature rewrite needed. @prashilthul, sorry the earlier guide work overlapped after you volunteered. The guide is already integrated, so please pick #73 or #74 if either suits your platform/language experience. Your privacy-test contribution is already credited in the merged support bundle.
prashilthul commentedon Oct 31, 2026
Thanks @shrey16 , and no worries about the overlap.
I'm on Linux and I'm not a native Arabic speaker, so I'll leave #73 and #74 for someone better placed to verify them. I'll keep an eye on the open issues and contribute wherever I can be useful, and I'll comment before starting anything so we don't duplicate work. If there's somewhere you'd especially like help, I'm happy to take a look.