Skip to content

T3/system path backend - #401

Closed
thomas9120 wants to merge 7 commits into
mainfrom
t3/system-path-backend-stage-one
Closed

thomas9120 wants to merge 7 commits into
mainfrom
t3/system-path-backend-stage-one

Conversation

@thomas9120

Copy link
Copy Markdown
Owner

No description provided.

- Classify System as externally managed and resolve known tools from PATH
- Handle unavailable PATH tools across status, runtime, and launch checks
- Add isolated discovery coverage for platform lookup and path precedence
- Check PATH executables with bounded `--version` probes and cache results by file identity
- Use the discovered System tools for launch and memory-estimator validation
- Probe llama-server before switching and rediscover System tools on startup
- Report tool availability and PATH guidance in status
- Keep System tools out of install and update flows
- Add frontend coverage for System backend activation and per-tool availability
- Gate launch and benchmark behavior using each tool’s detected build tag
- Add representative System layout coverage for server-only, complete, symlink, wrapper, broken, and updated tools
- Extend flag runner fixtures for PATH selection without repository fallback
@thomas9120

Copy link
Copy Markdown
Owner Author

After a thorough review I've determined this adds a significant maintenance burden for a relatively niche feature. I'm shelving it for now.

@thomas9120 thomas9120 closed this Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant