glue-fast
v0.3.1
Published
Install source-defined Glue skills and agents and configure GitHub Actions.
Readme
Glue CLI
The npm package is glue-fast; its installed command is glue. Requires Node.js 24 or newer.
From a project home, install the latest release with its repository name:
npx glue-fast install-skills 'brickspacelab/storeskills'Bare owner/repository targets default to https://glue.fast on first use. An explicit --site, GLUE_SITE, or saved login site overrides that default. Domain-qualified targets select their own HTTPS origin and resolve the owner/repository release. Explicit /s/<project> URLs and self-hosted origins remain supported. The install-skills and install-plugin commands require glue-fast 0.2.0 or later. Version 0.3.1 accepts pasted targets wrapped in matching smart quotes and installs into your home directory when run from the filesystem root.
Install a published project's authored skills in your codebase:
npx glue-fast install-skills https://your-glue-host/s/your-projectThat installs the available authored skills. To select one skill:
npx glue-fast install-skills https://your-glue-host/s/your-project --skill audit-shopifyOnly root skills/<name>/SKILL.md folders are installable skills. Each entrypoint needs a frontmatter name matching its folder and a description; its supporting files stay inside that folder. Ordinary Markdown outside these skill folders remains documentation and is never converted into a skill. If a release contains no skills, the command prints No skills found. and writes no installation files. Project and page views omit skill installation commands when nothing is installable.
Install the source-defined agent or native plugin:
npx glue-fast install-plugin https://your-glue-host/s/your-projectUse the arrow keys and Enter when prompted to choose Codex or Claude, or pass --agent codex or --agent claude. Native plugins use ~/.glue/plugins/ when run from the filesystem root or when permissions block the project-local plugin directory. Standalone skills installed from the filesystem root go into ~/.agents/skills/ or ~/.claude/skills/. The older add-skill, add-plugin and add-agent commands remain supported. Use --version <version> to install a specific release.
Codex and Claude plugin manifests are preserved from the published source commit. Restart your coding agent after native registration.
Set up the source-defined GitHub Action:
npx glue-fast init-ci https://your-glue-host/s/your-projectThe command creates a pinned workflow and prints required secrets. A task can bundle its action inside its skill (uses: "./skills/<name>/ci" in root glue.json), so its scripts and instructions ship in the same release without an extra action repository. External actions pinned to a full commit SHA remain supported. See repository-defined installation. Existing workflows are preserved. Review, commit and push the generated files.
Use --free for free content or --premium for the complete paid projection. When access is needed, the CLI signs in once if it must (approval continues to the release's access page in the same tab), prints and opens the access link, and installs the same release once the server confirms access. --no-browser prints the link and still waits. Revoked access and tiers that aren't for sale stop at once. Purchases require the creator's checkout to be enabled; the CLI never grants access itself. CI uses a GLUE_INSTALL_TOKEN secret instead of browser sign-in; create it with glue login --site https://your-glue-host --install-only | gh secret set GLUE_INSTALL_TOKEN.
Publishing and source-grounded docs are also available through publish, sync, docs, search, ask, mcp and mcp-config. Run --help for the command overview.
Sign in for docs and MCP
docs, search, ask and mcp need a customer token for a member of the project or a subscriber to its top tier. Sign in once per Glue host:
npx glue-fast login --site https://your-glue-hostThe browser approval stores a customer token locally until revoked, and the commands send it to that host. On another machine or in CI, set GLUE_CUSTOMER_TOKEN with GLUE_SITE naming the same host. logout removes the local token; revoke the terminal under Authorized devices to disable it. Customer-token reading, glue token, --install-only and the GLUE_SITE check arrive with the release after 0.1.1.
Publish from an agent
Publishing is part of the normal login. Log in, then register the generated configuration in your MCP host:
npx glue-fast login --site https://glue.fast
npx glue-fast mcp-config --site https://glue.fastIf you own or administer a project, the browser approval also offers
publishing. All your projects, the default, covers every project you own or
administer when the agent calls, including ones you add or are made an admin of
later. Specific projects starts with none ticked: tick the ones it may publish
to, or tick none for a login without publishing. Approval saves a separate
origin-bound publishing credential that lasts 90 days; the login then says
whether this terminal can publish. The stdio bridge (glue mcp --site
https://glue.fast) reads only that credential, and the generated configuration
contains no token. Connect through the bridge: an HTTP client pointed at
/api/glue/mcp sends no Glue login and is refused. glue token prints only the customer token. Use the same
--config-dir for login and MCP if the host needs a custom credential path.
Each machine needs its own browser approval. Installing a plugin that bundles the
publishing connection opens this login in your browser when no publishing
credential is saved where that connection reads it, and saves it there; in CI, with --no-browser or --free, it prints the
glue login step instead. See
Publish from an agent for
its tools and limits. These commands need a glue-fast release that includes
them.
Devices lists the customer login and the (publishing) credential separately;
revoke either alone. glue logout --site https://glue.fast removes both local
credentials. A later glue login that grants no publishing removes the saved
publishing credential; its approval stays valid until revoked under Devices or
expired.
When your Glue host changes
Sign in again with glue login --site https://your-new-glue-host, then use that origin in project URLs and --site arguments. Saved customer logins belong to their original origin; do not copy credential files or expect a redirect to transfer the login.
Update GLUE_SITE, MCP server URLs and any vendored workflow project URLs deliberately. Earlier CLI releases use --space / GLUE_SPACE for docs, publishing and MCP; 0.2.0 supports --project / GLUE_PROJECT while retaining the old aliases. Check the installed version's --help before changing those arguments.
The CLI rejects API redirects, and publishing/install secrets have different capabilities from customer logins. Existing self-hosted and local origins remain supported. Operators can use the platform domain cutover runbook to plan compatibility and rollback.
Node.js 24 or newer is required. See authoring skills and source configuration.
Public Free skills and native plugin installs finish without opening pricing or waiting for account approval. A mixed release prints a link to its plans and a pinned --premium command for an explicit upgrade. If that command needs access, connect the intended account in the browser and continue to the required offer. The installer resumes the same release after verified access. If the terminal stops while waiting, rerun its printed command. CI and install-token runs exit when access is missing. Locally modified files are preserved. These changes require the next npm CLI release.
