# Pungyo — Run Guide (server)

Pungyo runs as a local OpenAI-compatible HTTP server. You provide the model
GGUF and the two CUDA runtime DLLs in the same folder as the `.exe`.

## 1. Folder layout

Put these in one folder (call it whatever):

```
.\
├── pungyo-server-single.exe   (or pungyo-server-twin.exe — or both)
├── cublas64_13.dll
├── cublasLt64_13.dll
└── Qwen3.6-35B-A3B-Q4_K_M.gguf
```

All four (or five) files in the SAME directory.

## 2. Pick a profile, start the server

Open PowerShell in that folder.

```powershell
# single profile — maximum speed (~34.5 tok/s, ~7 GB VRAM)
.\pungyo-server-single.exe -m .\Qwen3.6-35B-A3B-Q4_K_M.gguf --port 8080 --host 127.0.0.1 -c 4096

# twin profile — stability-first (~28.5 tok/s, ~3.7 GB VRAM)
.\pungyo-server-twin.exe   -m .\Qwen3.6-35B-A3B-Q4_K_M.gguf --port 8080 --host 127.0.0.1 -c 4096
```

The server takes ~30-60 seconds to load the model. You'll see logs end with
`HTTP server is listening` — that means it's ready.

The operating point is chosen automatically in memory, never on the command
line. The two `.exe` files are siblings of the same engine; the file name
selects the profile.

## 3. Use it

| client | how |
|---|---|
| **Browser** | open `http://localhost:8080` (built-in chat) |
| **Cursor / Continue / ChatBox / Open WebUI / Jan** | set OpenAI base URL to `http://localhost:8080/v1` |
| **LangChain / OpenAI SDK / raw HTTP** | `POST http://localhost:8080/v1/chat/completions` (OpenAI schema) |

Stop with `Ctrl+C` in the server window.

## 4. Common flags

| flag | meaning |
|---|---|
| `-m PATH` | path to the GGUF |
| `--port N` | HTTP port (default 8080) |
| `--host 127.0.0.1` | localhost only (recommended) |
| `--host 0.0.0.0` | reachable from your LAN — add `--api-key ...` if you do this |
| `-c N` | context window in tokens (default 4096, max model trains to 262144) |
| `--api-key KEY` | require this key in `Authorization: Bearer KEY` |

## Notes

- Requires Windows + NVIDIA RTX-class 8GB GPU + recent NVIDIA driver.
- 32 GB system RAM recommended.
- Speed is a local observation and varies by hardware.
- The mechanism is not documented here by design (patent-filed).
- Issues / requests: use the repository Community tab.