Deep-ai-inc/ch.at

---

Deep-ai-inc/ch.at.json

{
  "createdAt": "2025-06-18T00:03:03Z",
  "defaultBranch": "master",
  "description": "Universal Basic Chat",
  "fullName": "Deep-ai-inc/ch.at",
  "homepage": null,
  "language": "Go",
  "name": "ch.at",
  "pushedAt": "2025-11-26T01:08:43Z",
  "stargazersCount": 1027,
  "topics": [],
  "updatedAt": "2025-11-26T02:02:04Z",
  "url": "https://github.com/Deep-ai-inc/ch.at"
}

ch.at - Universal Basic Intelligence

A lightweight language model chat service accessible through HTTP, SSH, DNS, and API. One binary, no JavaScript, no tracking.

Usage

# Web (no JavaScript)
open https://ch.at

# Terminal
curl ch.at/?q=hello             # Streams response with curl's default buffering
curl -N ch.at/?q=hello          # Streams response without buffering (smoother)
curl ch.at/what-is-rust         # Path-based (cleaner URLs, hyphens become spaces)
ssh ch.at

# DNS tunneling
dig @ch.at "what-is-2+2" TXT

# API (OpenAI-compatible, see https://platform.openai.com/docs/api-reference/chat/create)
curl ch.at/v1/chat/completions --data '{"messages": [{"role": "user", "content": "What is curl? Be brief."}]}'

Design

• ~1,300 lines of Go, three direct dependencies
• Single static binary
• No accounts, no logs, no tracking
• Configuration through source code (edit and recompile)

Privacy

Privacy by design:

• No authentication or user tracking
• No server-side conversation storage
• No logs whatsoever
• Web history stored client-side only

⚠️ PRIVACY WARNING: Your queries are sent to LLM providers (OpenAI, Anthropic, etc.) who may log and store them according to their policies. While ch.at doesn’t log anything, the upstream providers might. Never send passwords, API keys, or sensitive information.

Current Production Model: OpenAI’s GPT-4o. We plan to expand model access in the future.

Installation

Quick Start

# Copy the example LLM configuration (llm.go is gitignored)
cp llm.go.example llm.go

# Edit llm.go and add your API key
# Supports OpenAI, Anthropic Claude, or local models (Ollama)

# For HTTPS, you'll need cert.pem and key.pem files:
# Option 1: Use Let's Encrypt (recommended for production)
# Option 2: Use your existing certificates
# Option 3: Self-signed for testing:
#   openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -nodes

# Build and run
go build -o chat .
sudo ./chat  # Needs root for ports 80/443/53/22

Testing

# Build the self-test tool
go build -o selftest ./cmd/selftest

# Run all protocol tests
./selftest http://localhost

# Test specific queries
curl localhost/what-is-go
curl localhost/?q=hello

High Port Configuration

To run without sudo, edit the constants in chat.go:

const (
    HTTP_PORT   = 8080  // Instead of 80
    HTTPS_PORT  = 0     // Disabled
    SSH_PORT    = 2222  // Instead of 22
    DNS_PORT    = 0     // Disabled
)

Then build:

go build -o chat .
./chat  # No sudo needed for high ports

# Test the service
./selftest http://localhost:8080

Deployment

Nanos Unikernel (Recommended)

Deploy as a minimal VM with just your app:

# Install OPS
curl https://ops.city/get.sh -sSfL | sh

# Create ops.json with your ports
echo '{"RunConfig":{"Ports":["80","443","22","53"]}}' > ops.json

# Test locally
CGO_ENABLED=0 GOOS=linux go build
ops run chat -c ops.json

# Deploy to AWS
ops image create chat -c ops.json -t aws
ops instance create chat -t aws

# Deploy to Google Cloud
ops image create chat -c ops.json -t gcp
ops instance create chat -t gcp

Traditional Deployment

# Systemd service
sudo cp chat /usr/local/bin/
sudo systemctl enable chat.service

# Docker
docker build -t chat .
docker run -p 80:80 -p 443:443 -p 22:22 -p 53:53/udp chat

Configuration

Edit constants in source files:

• Ports: chat.go (set to 0 to disable)
• Rate limits: util.go
• Remove service: Delete its .go file

Limitations

• DNS: Responses limited to ~500 bytes. Complex queries may time out after 4s. DNS queries automatically request concise, plain-text responses
• History: Limited to 64KB to ensure compatibility across systems
• Rate limiting: Basic IP-based limiting to prevent abuse
• No encryption: SSH is encrypted, but HTTP/DNS are not

License

MIT License - see LICENSE file

Contributing

Before adding features:

• Does it increase accessibility?
• Is it under 50 lines?
• Is it necessary?