Repository navigation
gsd-reasonix — GSD for Reasonix (EoS host integration) #3379
onionviolet
started this conversation in
EoS Registry
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Repo: https://github.com/onionviolet/gsd-reasonix
Release: https://github.com/onionviolet/gsd-reasonix/releases/tag/v1.0.0
License: MIT · protocolVersion: 1 · enginesGsd:
>=1.10.0Reasonix is a Go, single-static-binary, DeepSeek-native terminal coding agent. This integration renders the GSD workflow set as native Reasonix slash-command launchers. GSD workflows are not reimplemented: they stay in
~/.claude/gsd-core/workflows/, and each launcher maps their host-neutral instructions onto Reasonix's own tools (task/fleetfor subagents,askfor questions,todo_writefor plans,complete_stepfor evidence-backed sign-off).Declared axes
Every value below is sourced from Reasonix's own documentation (
docs/SPEC.md,docs/GUIDE.md,docs/CONFIG_PATHS.md,CONTRIBUTING.md), per the "never infer" rule.embeddingModedeclarativecommandSurfaceslash-filemodelModepassivehookBushoststateIOfilesystemtransportmcpruntimegointerfacePoints:command,artifact.profile:declarative-cli.effortSurfaceis deliberately omitted. Reasonix resolves effort from config (supported_efforts/default_effort) and the/effortcommand, with no argv route, so neitherargvnornoneis a documented fit and the field is optional.Known limitation, stated up front
Reasonix's docs do not state its subagent toolkit or whether a background-dispatched subagent may spawn further subagents. Under
shouldFlattenDispatchthat fails closed, so the orchestrator runs inline rather than backgrounded. That is the correct conservative outcome given the documentation, not a bug. Getting it lifted means an upstream documentation change in Reasonix itself, and I will revise the entry if that lands.Install
Uninstall removes only the launchers the package ships, and removes its
[skills] excluded_pathsline only when it is still the one the installer wrote. Hand-writtengsd-*skills and user-edited config values are left in place.npm testruns 14 checks over the launcher set and the install round-trip against a throwawayREASONIX_HOME.Context
This supersedes #3346, which proposed an in-tree
capabilities/reasonix/capability.jsonand was correctly closed as filed against the wrong surface. Per ADR-1239 this ships as an out-of-tree host-plugin listed in the EoS Registry. Registry PR to follow.All reactions