Skip to content
Siglata Docs
English
Esc
navigateopen⌘Jpreview
On this page

General Installers

Architecture, multi-agent detection, and automated distribution for Siglata installers.

Siglata delivers two canonical installer pipelines hosted directly from the production domain:

Pipeline Target Environments POSIX Shell Command Windows PowerShell Command
Codex & ChatGPT Local .codex environment curl -fsSL https://www.siglata.com/install | sh irm https://www.siglata.com/install.ps1 | iex
Universal Multi-Agent Claude Code, Cursor, Codex, VS Code, Hermes, Grok, OpenClaw, NanoClaw, OMP, Kiro curl -fsSL https://www.siglata.com/install/plugins | sh irm https://www.siglata.com/install/plugins.ps1 | iex

1. Universal Multi-Agent Installer (/install/plugins)

The Universal Installer conforms to the Agent Plugins specification and Agent Skills standard. It automatically discovers coding agents on your machine and installs both the Agent Skill and the Model Context Protocol (MCP) server configuration.

Smart Single-Choice Bypass

To provide a seamless experience for non-technical users, the installer avoids unnecessary questions:

  • 1 Agent Detected: If you only have one supported agent installed (for example, only Cursor or only Codex), the installer automatically configures that agent with zero prompts.

  • 0 Agents Detected: If no specific agent configuration directories are found, the installer automatically stages files into the Universal Agent Skills directory (~/.agents/skills) without prompting.

  • Multiple Agents Detected: If you have two or more agents (e.g. Cursor and Claude Code), the installer displays an interactive numbered menu:

    Siglata detected multiple AI coding agents on this machine:
      [1] Claude Code
      [2] Cursor
      [a] All detected agents (Recommended)
    
    Which ones do you want to install into? [default: a]:

What It Installs

For each selected agent, the installer configures:

  1. Agent Skills: Stages skills/siglata/SKILL.md and operations.md into the agent’s skills directory.
  2. MCP Server: Configures the siglata MCP server pointing to https://www.siglata.com/v1/mcp with type: "streamable-http".

Installation Scope

  • Global Scope (~/.<agent>/skills): The default mode. Skills and MCP configurations are available across all your projects.
  • Project Scope (./.<agent>/skills): When run inside an existing Git repository, the installer prompts whether to install globally or in the active repository.

2. Standalone Compiled Executables (For Non-Technical Users)

For users who prefer native executables over shell commands, Siglata provides precompiled, signed binaries:

  • Windows: siglata-installer.exe — precompiled with Bun (--target=bun-windows-x64) and code-signed via Azure Trusted Signing with RFC 3161 timestamps.
  • macOS: siglata-installer-darwin — precompiled with Bun (--target=bun-darwin-arm64 and bun-darwin-x64), signed with Apple Developer ID, and notarized by Apple Gatekeeper.
  • Linux: Standalone static ELF binaries for x86_64 and aarch64.

These executables run an interactive terminal wizard built with pure Effect that walks users through agent selection with clear visual confirmations.


3. Dedicated Codex Installer (/install)

The dedicated /install pipeline specifically manages the local OpenAI Codex environment ($CODEX_HOME or ~/.codex):

  • Merges [mcp_servers.siglata] into config.toml idempotently using AST and awk parsing.
  • Stages the local marketplace and plugin cache at ~/.codex/siglata-marketplace.
  • Adds the Siglata managed instructions block to ~/.codex/AGENTS.md.
  • Backs up previous configurations to config.toml.siglata-backup.

Was this page helpful?