Skip to content

[pull] main from Alishahryar1:main - #247

Merged
pull[bot] merged 2 commits into
Co-Contribute-OpenSource:mainfrom
Alishahryar1:main
Sep 26, 2026
Merged

pull[bot] merged 2 commits into
Co-Contribute-OpenSource:mainfrom
Alishahryar1:main

Conversation

@pull

@pull pull Bot commented Sep 26, 2026 •

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Why

Bug reports need FCC configuration and environment details without
making users collect settings by hand. Installation failures need a
simpler form because FCC commands may not be available yet.

## How

Add `fcc-doctor` to print indented JSON with the FCC version first and
copy it to the clipboard. Collect saved settings with current terminal
overrides, provider configuration, routing, reasoning, web tools,
integration state, system information, and bounded native harness
version probes. Explicit projections exclude credentials, account
identities, file paths, logs, and code sessions. The command works
without a running server, leaves configuration unchanged, and preserves
printed output when clipboard access is unavailable.

Add an installation form with one required description and a
post-install form with exactly two required fields: description and
doctor JSON. Read the version reminder from that JSON, exempt
installation reports, and retain support for edits to existing issue
forms. Register the command in the installers and uninstallers and add
its README usage command.






<!-- greptile_comment -->

<!-- greptile_summary -->

<h2><a
href="https://app.greptile.com/api/retrigger?id=69744844"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source
media="(prefers-color-scheme: light)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img
alt="Retrigger"
src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"
align="right"></picture></a>Confidence Score: 5/5</h2>

<!-- greptile-risk -->

Safe to merge; the remaining diagnostic inaccuracy is non-blocking.

<h2><a
href="https://app.greptile.com/api/ide/codex?prompt=IMPORTANT%3A%20Work%20in%20the%20repository%20%22alishahryar1%2Ffree-claude-code%22%20on%20the%20existing%20branch%20%22ali%2Ffcc-doctor%22.%20Checkout%20that%20branch%20%E2%80%94%20do%20NOT%20create%20a%20new%20branch%20or%20open%20a%20new%20PR.%20Push%20your%20changes%20to%20%22ali%2Ffcc-doctor%22.%0A%0A%23%23%23%20Issue%201%0Asrc%2Ffree_claude_code%2Fruntime%2Fdiagnostics.py%3A254-255%0AIf%20a%20harness%20prints%20another%20tool%E2%80%99s%20version%20before%20its%20own%2C%20the%20doctor%20report%20takes%20the%20first%20version%20it%20finds%20and%20labels%20it%20as%20the%20harness%20version.%20A%20Codex%20response%20preceded%20by%20%60Node.js%20v22.4.0%60%20reports%20Codex%20as%20available%20at%20%6022.4.0%60%20instead%20of%20%600.45.0%60.%20This%20non-blocking%20error%20can%20mislead%20people%20using%20the%20report%20to%20diagnose%20an%20installation.%0A%0A---%0A%0AFor%20each%20issue%20above%2C%20determine%20whether%20it%20is%20valid%20and%20should%20be%20fixed.%20If%20so%2C%20fix%20it%20directly.&repo=alishahryar1%2Ffree-claude-code&pr=1906&platform=github"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/FixAllInCodexDark.svg?v=7"><source
media="(prefers-color-scheme: light)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/FixAllInCodex.svg?v=7"><img
alt="Fix All in Codex"
src="https://greptile-static-assets.s3.amazonaws.com/badges/FixAllInCodex.svg?v=7"
align="right"></picture></a>Findings</h2>

1. <img alt="P2"
src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=9"
align="top">&nbsp;**Unrelated version reported for harness** <a
href="https://github.com/Alishahryar1/free-claude-code/pull/1906#discussion_r4109983102">▶</a>

<details open><summary>Summary</summary>

The PR adds a shareable `fcc-doctor` report, separates installation and
post-installation issue forms, and updates version validation,
installers, and tests. One previously reported diagnostic inaccuracy
remains.
</details>

<!-- greptile_confidence_score:5 -->

<sub>Reviews (3) · Last reviewed commit: ["Synchronize API key rejection
test with
..."](https://github.com/alishahryar1/free-claude-code/commit/82b4315625581d86efd9a7e30274f219b143b3d2)</sub>

<!-- /greptile_comment -->
## Why

Installer subprocess checks take substantial time in regular CI. Make
them an opt-in local suite.

## How

Move the complete installer test folder, including fixtures, helpers,
and rules, from `tests/installers/` to `smoke/installers/`. Document the
explicit command to run it and update its rules for local-only
execution. Regular pytest continues to collect `tests/`, so these checks
no longer run in CI.
@pull pull Bot locked and limited conversation to collaborators Sep 26, 2026
@pull pull Bot added the ⤵️ pull label Sep 26, 2026
@pull
pull Bot merged commit ba4b934 into Co-Contribute-OpenSource:main Sep 26, 2026

This branch was successfully deployed

1 active deployment
pypi — ba4b9341 Deployed Sep 26, 2026 by pull[bot] via Publish to PyPI #4
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant