[codex] Remove app orchestration surface#47
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tycho is now positioned as
Tycho - Factorio for Agentsand the codebase has been stripped of the old app-orchestration surface. This removes Kamal/action handling, app config, app health/liveness endpoints, Rails/Docker/mise/version checks, and stale Remote UI/TUI project action paths.Impact
Projects now behave as agent workspaces with git metadata and managed-agent state. Operator-facing docs, examples, tests, and Remote UI copy no longer describe Tycho as an app or deployment tool.
Validation
node --check lib/hq/remote_ui/assets/app.jsbin/test