Skip to content

fix: simplify start - #14

Merged
ADITYA-tp01 merged 1 commit into
mainfrom
fix/simplify-start
Aug 29, 2026
Merged

fix: simplify start#14
ADITYA-tp01 merged 1 commit into
mainfrom
fix/simplify-start

Conversation

@ADITYA-tp01

@ADITYA-tp01 ADITYA-tp01 commented Aug 29, 2026

Copy link
Copy Markdown
Owner

User description

Manual TrueForge launch instead of broken auto-launch.


CodeAnt-AI Description

Simplify startup by requiring manual TrueForge launch

What Changed

  • The startup script still installs and verifies TrueForge in WSL, but no longer tries to launch it automatically.
  • After setup, the script gives step-by-step instructions for starting TrueForge in a new terminal.
  • Setup instructions now clearly separate starting TrueForge from configuring its UI and connected services.

Impact

✅ Fewer automatic launch failures
✅ Clearer startup instructions
✅ More reliable TrueForge initialization

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@ADITYA-tp01
ADITYA-tp01 merged commit 9c1942f into main Aug 29, 2026
@codeant-ai

codeant-ai Bot commented Aug 29, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 8c8b85c Aug 29, 2026 · 22:59 23:01

@codeant-ai

codeant-ai Bot commented Aug 29, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Aug 29, 2026
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Replace automatic TrueForge startup with manual launch instructions

🐞 Bug fix 📝 Documentation 🕐 Less than 10 minutes

Grey Divider

AI Description

• Remove unreliable automatic TrueForge launch through a temporary WSL script.
• Guide users through manual startup and existing TrueForge UI configuration.
Diagram

graph TD
  A["start.ps1"] -->|starts| B["Core services"] -->|prepares| C["WSL environment"] -->|installs| D["TrueForge package"] -->|instructs user| E["Manual launch"] -->|opens| F["TrueForge UI"] -->|configures| G["MCP connection"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Retain automatic WSL launch
  • ➕ Preserves a one-command startup experience.
  • ➕ Avoids asking users to manage another terminal.
  • ➖ Requires fragile cross-shell quoting, path translation, and process lifecycle handling.
  • ➖ Repeats the failure mode this fix intentionally removes.

Recommendation: Use the PR's manual handoff for reliability: provisioning remains automated while the unstable Windows-to-WSL process launch is eliminated. Automatic launch should only return if it can use a well-tested, persistent launcher with clear lifecycle and error handling.

Files changed (1) +13 / -22

Bug fix (1) +13 / -22
start.ps1Replace brittle TrueForge auto-launch with manual startup guidance +13/-22

Replace brittle TrueForge auto-launch with manual startup guidance

• Removes temporary Bash-script generation, WSL process spawning, and the launch delay. Updates completion output with explicit commands for starting TrueForge in a new WSL terminal, then preserves the UI configuration steps.

start.ps1

@github-actions

Copy link
Copy Markdown

Failed to generate code suggestions for PR

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Launches wrong WSL distro 🐞 Bug ≡ Correctness
Description
The setup installs Node.js and TrueForge in the distribution named Ubuntu, but the new manual step
runs plain wsl, which opens the user's default distribution. When another distribution is the
default, npx @truefoundry/trueforge runs in an environment this script never prepared and can fail
because Node/npm is absent or use an unrelated installation.
Code

start.ps1[91]

+Write-Host "    2. Type: wsl" -ForegroundColor White
Relevance

●●● Strong

Accepted WSL environment-selection concerns show the team values explicit, portable runtime
targeting; this is a concrete correctness bug.

PR-#5

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The script explicitly targets Ubuntu for both its Node.js check/install and its TrueForge
check/install, so only that distribution is guaranteed to contain the prerequisites. The newly added
plain wsl instruction does not preserve that distribution selection.

start.ps1[61-77]
start.ps1[89-93]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The manual instructions open the default WSL distribution even though the script installs all prerequisites specifically in the distribution named `Ubuntu`.

## Issue Context
Users with multiple WSL distributions can have a non-Ubuntu default, causing the subsequent TrueForge command to run in an unprepared environment.

## Fix Focus Areas
- start.ps1[89-93]

Change the instruction to `wsl -d Ubuntu`, or provide one command that explicitly invokes TrueForge in Ubuntu.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context sources
Review mode: ⚖️ Balanced

Grey Divider

Tip of the day
💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread start.ps1
Write-Host " 6. Enable approval for rollback_deploy, restart_service" -ForegroundColor White
Write-Host " Now start TrueForge manually:" -ForegroundColor Cyan
Write-Host " 1. Open a NEW terminal" -ForegroundColor White
Write-Host " 2. Type: wsl" -ForegroundColor White

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Launches wrong wsl distro 🐞 Bug ≡ Correctness

The setup installs Node.js and TrueForge in the distribution named Ubuntu, but the new manual step
runs plain wsl, which opens the user's default distribution. When another distribution is the
default, npx @truefoundry/trueforge runs in an environment this script never prepared and can fail
because Node/npm is absent or use an unrelated installation.
Agent Prompt
## Issue description
The manual instructions open the default WSL distribution even though the script installs all prerequisites specifically in the distribution named `Ubuntu`.

## Issue Context
Users with multiple WSL distributions can have a non-Ubuntu default, causing the subsequent TrueForge command to run in an unprepared environment.

## Fix Focus Areas
- start.ps1[89-93]

Change the instruction to `wsl -d Ubuntu`, or provide one command that explicitly invokes TrueForge in Ubuntu.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment thread start.ps1
Write-Host " 6. Enable approval for rollback_deploy, restart_service" -ForegroundColor White
Write-Host " Now start TrueForge manually:" -ForegroundColor Cyan
Write-Host " 1. Open a NEW terminal" -ForegroundColor White
Write-Host " 2. Type: wsl" -ForegroundColor White

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: The setup and installation steps explicitly target the Ubuntu WSL distribution, but the instructions launch the user's default distribution with plain wsl. If the default distribution is not Ubuntu, npx runs where Node.js and TrueForge were not installed, so the documented launch fails or starts a different environment. Launch the explicitly configured Ubuntu distribution instead. [api mismatch]

Severity Level: Major ⚠️
- ❌ TrueForge launch fails for non-Ubuntu WSL defaults.
- ⚠️ Manual startup can use the wrong Node.js environment.
- ❌ The TrueForge UI remains unavailable at localhost:3000.

Use CodeAnt Skill Fix in Cursor Fix in VSCode Claude

Prompt for AI Agent 🤖
This is a comment left during a code review.

**Path:** start.ps1
**Line:** 91:91
**Comment:**
	*Api Mismatch: The setup and installation steps explicitly target the `Ubuntu` WSL distribution, but the instructions launch the user's default distribution with plain `wsl`. If the default distribution is not Ubuntu, `npx` runs where Node.js and TrueForge were not installed, so the documented launch fails or starts a different environment. Launch the explicitly configured Ubuntu distribution instead.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
👍 | 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant