← gstack WorkflowsCONTENT HISTORY

Update to gstack Workflows

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "browse",
  "description": "Drive the native gstack browser when available; otherwise use host browser capabilities without pretending gstack is running.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 283
    }
  ],
  "skill_md_contents": "---\nname: browse\ndescription: Drive the native gstack browser when available; otherwise use host browser capabilities without pretending gstack is running.\n---\n\n# Browse\n\nPortable ChatGPT/Codex adaptation of the `browse` workflow from `garrytan/gstack`. Preserve the original job and safety intent while mapping execution to capabilities the current host actually exposes.\n\n## When to use\n\nUse this Skill when the user explicitly names `browse` or asks for the same job described above.\n\n## Host contract\n\n- Inspect repository or file evidence before making claims about the current state.\n- Use host-native read, list, search, grep, patch, write, shell, browser, computer, and Python capabilities only when they actually exist.\n- Never claim commands, tests, browser actions, device actions, file writes, Git operations, or external mutations that were not executed.\n- Prefer read-only discovery before mutation.\n- Respect repository instructions and preserve unrelated work.\n- When the original native gstack runtime is available in Codex, it may be used as an implementation detail after inspecting the installed upstream Skill. Do not hard-code Claude-only paths as a requirement.\n\n## Workflow\n\n1. Detect a compatible local gstack browser runtime and shell before invoking native commands.\n2. If present, follow the installed upstream gstack browser Skill and its safety controls.\n3. If absent but the host has another browser capability, perform the user job with that capability and state that it is not the native gstack browser.\n4. If neither exists, stop rather than fabricate browser execution.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n\n## Native bridge\n\nOn Codex, if a compatible original gstack runtime is installed and shell access exists, prefer its current `/browse` instructions. Otherwise use the host browser capability as the portable fallback.\n"
}

SHA-256: 1c04df02dde94c418c6a882856d05f61fa8113a8c5b546a82f4d78677fa71381