What Is Instagit? Understanding the Reasonix OpenRouter Client

Instagit is the branding identifier that the Reasonix project uses when registering with the OpenRouter API, specified via HTTP headers in the opencode.json configuration file.

Instagit functions as the public-facing portal and access layer for the Reasonix coding agent, an autonomous AI system maintained in the esengine/DeepSeek-Reasonix repository. While the Instagit brand surfaces Reasonix capabilities through its web interface, the technical integration relies solely on metadata headers that identify the client to OpenRouter, implementing no additional functional logic beyond this identification layer.

What Is Instagit?

Instagit is the commercial branding and client identification name for the Reasonix engine’s OpenRouter integration. According to the source code in esengine/DeepSeek-Reasonix, Instagit does not contain standalone logic; instead, it serves as the named entity that OpenRouter recognizes when processing API requests from Reasonix instances.

The name appears in the OpenRouter-App-Title header, while the associated URL (https://instagit.com) points to the public portal where users can access Reasonix’s autonomous coding capabilities. These capabilities include terminal-driven agents, desktop applications, browser-based UIs, and VS Code extensions—all operating under the Instagit brand while executing Reasonix core logic.

How Instagit Configures OpenRouter Headers

The Instagit identity is established in the opencode.json file located at the repository root. This configuration file defines the headers that Reasonix sends with every OpenRouter request:

{
  "headers": {
    "OpenRouter-App-Title": "Instagit",
    "OpenRouter-App-URL": "https://instagit.com"
  }
}

These headers serve two purposes. First, they identify the client application for analytics and routing on OpenRouter’s infrastructure. Second, they associate the traffic with the Instagit service domain, ensuring proper attribution and configuration retrieval.

Implementing Instagit in Reasonix Deployments

When deploying Reasonix locally or on your own infrastructure, you can configure these same headers in your reasonix.toml configuration file to maintain the Instagit identity or customize it for your own branding:

# reasonix.toml – config example

[provider.openrouter]
options.headers.OpenRouter-App-Title = "Instagit"
options.headers.OpenRouter-App-URL   = "https://instagit.com"

After configuring the headers, launching the Reasonix engine will automatically include these identifiers in all OpenRouter API requests:

# Launch Reasonix (CLI/TUI) – it will read the above config

reasonix

Key Files and Source Locations

Understanding the Instagit integration requires examining these specific files in the esengine/DeepSeek-Reasonix repository:

• opencode.json — Contains the canonical OpenRouter header definitions that establish "Instagit" as the OpenRouter-App-Title and https://instagit.com as the application URL.
• README.md — Documents the Reasonix project architecture, explaining how the engine supports multiple interfaces (terminal, desktop, browser, VS Code) that are surfaced through the Instagit portal.
• reasonix.toml (user configuration) — The deployment-specific file where operators can override or confirm the Instagit headers for their OpenRouter provider connections.

Summary

• Instagit is the branded client identifier for Reasonix’s OpenRouter integration, not a separate codebase.
• The identity is configured via the OpenRouter-App-Title and OpenRouter-App-URL headers in opencode.json.
• Users access Reasonix’s autonomous coding capabilities through the Instagit portal at https://instagit.com, but the functional logic resides entirely within the Reasonix engine.
• Deployments can replicate this configuration in reasonix.toml to maintain consistent API identification.

Frequently Asked Questions

Is Instagit a separate application from Reasonix?

No. Instagit is strictly a branding and identification layer. It does not implement autonomous coding logic, reasoning engines, or UI components. The actual functionality—including code generation, terminal interaction, and IDE extensions—lives entirely within the Reasonix binary and its plugins. Instagit serves only as the named entity that identifies these requests to OpenRouter.

Where is the Instagit configuration defined in the repository?

The configuration is located in opencode.json at the repository root. This file sets the OpenRouter-App-Title header to "Instagit" and the OpenRouter-App-URL to "https://instagit.com", which OpenRouter uses to identify and route requests from Reasonix clients.

Do I need to configure Instagit headers to use Reasonix with OpenRouter?

Yes, if you want your deployment to identify as Instagit when using OpenRouter as a provider. You must set the OpenRouter-App-Title and OpenRouter-App-URL headers in your reasonix.toml file under the [provider.openrouter] section. These headers inform OpenRouter which client application is initiating the request.

What capabilities does the Instagit portal provide?

The Instagit portal (https://instagit.com) provides the user-facing access point for Reasonix’s features, including autonomous code generation, terminal-based agents, desktop applications, browser interfaces, and VS Code extensions. However, these capabilities are executed by the Reasonix engine; Instagit itself functions purely as the branded gateway and metadata identifier for the service.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}