# Headless Client

### Introduction to the Headless Client

The headless client is a foundational component of Chain Tactics, designed to empower developers and extend the game’s ecosystem in a fully modular, platform-agnostic way. By decoupling game logic from the user interface, it enables seamless interaction with Chain Tactics’ smart contracts, powered by the Sovrun SDK’s MUD Engine, without requiring direct blockchain expertise (See [Sovrun SDK](/build-with-sovrun/chain-tactics/sovrun-sdk.md)for details).

At its core, the headless client serves as a bridge between on-chain game logic and external applications, allowing for:

* Flexible Development: Developers can build their own front-end experiences, AI-driven agents, or automation tools without modifying core game mechanics, supported by the SDK’s Game IDE Integrator for Unity and other platforms.
* Multi-Platform Expansion: Since it’s written in C#, the client can be integrated across various devices and interfaces, ensuring broad accessibility.
* Decentralized Evolution: As Chain Tactics enters its open-source co-development phase, this tool enables community-driven innovation by providing a standardized yet adaptable framework for new game extensions, AI opponents, or even alternative gameplay modes.

By abstracting blockchain complexities, the headless client simplifies development while preserving the integrity of the game’s Autonomous World framework—ensuring Chain Tactics remains dynamic, scalable, and truly owned by its community.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sovrun.org/build-with-sovrun/chain-tactics/headless-client.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.