farhoodlabs/devcontainer
8
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

Support Crush as an IDE option #50

New Issue
Open
opened 2026-02-24 04:16:28 +00:00 by cpfarhood · 2 comments
cpfarhood commented 2026-02-24 04:16:28 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

Add crush as a valid ide.type option alongside vscode, antigravity, and none. Crush is already installed in the Docker image but can only be used by manually launching it from a terminal. It should be a first-class IDE choice that launches automatically on container start.

Current Behavior

  • ide.type: vscode → launches VSCode via VNC
  • ide.type: antigravity → launches Google Antigravity via VNC
  • ide.type: none → no IDE, sleep infinity
  • Crush is installed at /usr/local/bin/crush but has no IDE integration

Proposed Behavior

  • ide.type: crush → launches Crush as the primary interface

Implementation Notes

Crush is a terminal-based AI coding agent (successor to OpenCode), not a GUI IDE. This means:

  1. No VNC needed — Crush runs in a terminal, similar to ide.type: none but with an active process
  2. Access via SSH or kubectl exec — users would connect via SSH (ssh.enabled: true) or kubectl exec rather than port 5800
  3. Liveness probe adjustment — with no VNC on port 5800, the probe should fall back to the SSH/TCP check (already handled by the none path)

Changes Required

  • scripts/startapp.sh: Add crush) case to the IDE switch: 
    crush)
    echo "Launching Crush in: $WORKSPACE_DIR"
    cd "$WORKSPACE_DIR"
    exec crush
    ;;
  • chart/values.schema.json: Add "crush" to the ide.type enum
  • chart/values.yaml: Update comment to list crush as an option
  • Documentation: Update README.md and CLAUDE.md IDE references

Open Questions

  • Should ssh.enabled automatically be set to true when ide.type: crush? Terminal-only mode is most useful with SSH access.
  • Should we also add claude as an IDE type for the same pattern? (Claude Code is also a terminal agent installed in the image)
## Summary Add `crush` as a valid `ide.type` option alongside `vscode`, `antigravity`, and `none`. Crush is already installed in the Docker image but can only be used by manually launching it from a terminal. It should be a first-class IDE choice that launches automatically on container start. ## Current Behavior - `ide.type: vscode` → launches VSCode via VNC - `ide.type: antigravity` → launches Google Antigravity via VNC - `ide.type: none` → no IDE, `sleep infinity` - Crush is installed at `/usr/local/bin/crush` but has no IDE integration ## Proposed Behavior - `ide.type: crush` → launches Crush as the primary interface ### Implementation Notes Crush is a terminal-based AI coding agent (successor to OpenCode), not a GUI IDE. This means: 1. **No VNC needed** — Crush runs in a terminal, similar to `ide.type: none` but with an active process 2. **Access via SSH or `kubectl exec`** — users would connect via SSH (`ssh.enabled: true`) or `kubectl exec` rather than port 5800 3. **Liveness probe adjustment** — with no VNC on port 5800, the probe should fall back to the SSH/TCP check (already handled by the `none` path) ### Changes Required - **`scripts/startapp.sh`**: Add `crush)` case to the IDE switch: ```bash crush) echo "Launching Crush in: $WORKSPACE_DIR" cd "$WORKSPACE_DIR" exec crush ;; ``` - **`chart/values.schema.json`**: Add `"crush"` to the `ide.type` enum - **`chart/values.yaml`**: Update comment to list `crush` as an option - **Documentation**: Update README.md and CLAUDE.md IDE references ### Open Questions - Should `ssh.enabled` automatically be set to `true` when `ide.type: crush`? Terminal-only mode is most useful with SSH access. - Should we also add `claude` as an IDE type for the same pattern? (Claude Code is also a terminal agent installed in the image)
cpfarhood commented 2026-02-24 11:16:46 +00:00 (Migrated from github.com)
Copy Link
Copy Source

You may still need to restart the crush app during usage, might be smarter to have a terminal with ssh instead. Covers all the CLI based options.

You may still need to restart the crush app during usage, might be smarter to have a terminal with ssh instead. Covers all the CLI based options.
cpfarhood commented 2026-02-24 13:25:57 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Let's use the WEB_TERMINAL option here for terminal based clients.
https://github.com/jlesage/docker-baseimage-gui?tab=readme-ov-file#environment-variables

Let's use the WEB_TERMINAL option here for terminal based clients. https://github.com/jlesage/docker-baseimage-gui?tab=readme-ov-file#environment-variables
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
antigravity
architecture
automation
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 examples
good first issue
Good for newcomers
 helm
help wanted
Extra attention is needed
 invalid
This doesn't seem right
 maintainability
monitoring
question
Further information is requested
 refactor
tooling
user-experience
validation
wontfix
This will not be worked on
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
fl_blake (Blake MIddleware) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) flux (Flux CD) admin (Gitea Admin) fl_hugh (Hugh Commit) renovate (Mend Renovate) fl_warren (Warren Bufferpool)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: farhoodlabs/devcontainer#50
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?