Skip to content

refactor(agents): remove Ruby from the shared runtime tooling #5738

Open

Description

@purp

User Story

As an OpenShell maintainer reviewing and running Gator and the shared agent runtime, I want fewer host dependencies so launching agents and running their regression tests do not require Ruby.

Description

Investigate replacing Ruby in the shared agent launcher, image handling, and related tests. This is optional cleanup for later consideration, not a prerequisite for the layout migration or runtime generalization in #5723.

JSON handling

The Ruby uses in scripts/agents/image.sh parse gateway compute drivers, k3d cluster status, and image repository digests. These appear suitable for jq, a narrower dependency already used by the agent tooling. Preserve validation and failure behavior rather than merely extracting fields.

Use jq for JSON-only operations in scripts/agents/run.sh where appropriate, including credential-file queries and tooling metadata generation.

YAML and launcher logic

Choose a replacement for the YAML manipulation in scripts/agents/run.sh before implementing this work. It currently reads manifests and provider profiles, updates provider-profile YAML, resolves profile paths, and produces shell-escaped scalar and array assignments. Evaluate a YAML-specific tool against an existing supported language with a YAML library; document the dependency and installation trade-offs rather than assuming jq can process YAML directly.

Ruby also assembles prompt templates and subagent commands and edits staged Dockerfiles. Account for those uses when choosing replacements; replacing only the YAML parser will not remove the dependency.

Tests and documentation

Remove the Ruby YAML assertions in the Gator feedback-ledger and thread-resolution tests. After the layout migration, these live under .agents/agents/gator/tests/; shared launcher and image tests remain under scripts/agents/ unless runtime generalization moves them.

Context

Definition of Done

  • Choose and document the YAML replacement and its host installation requirements.
  • Remove Ruby from the shared launcher, image handling, and associated tests.
  • Preserve YAML types, shell quoting, literal prompt handling, credential confidentiality, Dockerfile final-user handling, and fail-closed validation.
  • Preserve gateway/cluster selection and image-digest validation behavior.
  • Explicitly selected launcher, image, supervisor, harness, and guarded-helper suites pass on a host without Ruby.
  • Setup documentation and prerequisite checks describe only the dependencies still required.

Activity

  1. self-assigned this
    on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions