docs(windows): expand windows.md with kernel bootstrap, env inheritance, lock cleanup - #962
docs(windows): expand windows.md with kernel bootstrap, env inheritance, lock cleanup#962abdulazizFarhan wants to merge 1 commit into
Conversation
|
Hi, thanks for taking the time to contribute to Prime Agent! Since open sourcing the project, we’ve received far more pull requests than we can responsibly review and validate. Prime Agent runs directly on users’ machines, so we need to be deliberate about which changes we accept and how they are reviewed. Rather than leave a large backlog that we cannot meaningfully work through, we’re closing the current PR queue and moving to a discussion-first contribution process. We have established new contribution guidelines to help us continue iterating on Prime Agent and better manage contributions from the community. Going forward, we won’t review unsolicited pull requests. Instead, please start with a GitHub Discussion. We’ll identify recurring bugs and feature requests, create Issues for work we want to pursue, and invite pull requests from maintainers or vouched contributors when implementation is ready. Please read the full process documented in our contribution guidelines. While we’re closing this backlog, we’re still reviewing it at a high level to identify recurring bugs, useful ideas, and important problems that we should address ourselves. Thanks again for the time you put into this! |
Expands
packages/coding-agent/docs/windows.mdwith the IPython kernel bootstrap workflow for Windows.Added sections:
tyroanddillcalled out as the easy ones to miss (Prime Agent's bootstrap only reports the first missing group per run).setxwrites a user-level var, but PowerShell does NOT auto-inherit user-level vars into the process env (cmddoes). The wrapper must explicitly copy them via[System.Environment]::SetEnvironmentVariable($name, $value, 'Process'). This is the most common silent failure for PowerShell-launchedprime-agentsessions.session-leases/*.lockcleanup.proper-lockfileuses directories as locks on Windows. If the previousprime-agentwas killed, the.lockdirectory blocks the next resume withEPERM: rename *.lock.candidate-XXX → *.lock. Wrapper should clear locks whoseowner.jsonPID is no longer running.Why docs-only: the kernel path fix itself is already in PR #825 (
fix/windows-console-flicker). This PR makes the existing workaround discoverable and documents the PowerShell + lock gotchas that bit me during setup. Closes the documentation gap for #660.Note
Expand Windows documentation with kernel bootstrap, env inheritance, and lock cleanup
Adds several new sections to windows.md covering the full Windows setup and troubleshooting workflow:
prime-agent, addressing env inheritance gaps on Windows*.lockdirectories whose owning PID no longer exists.bootstrap-versionMacroscope summarized f366c91.