.env.example

# =============================================================
#  HPC-Relay Configuration
#  Copy this file to .env and fill in your values.
#  NEVER commit .env -- it contains secrets.
# =============================================================

# --- Telegram (REQUIRED) ---
# Get from @BotFather on Telegram (/newbot)
TELEGRAM_BOT_TOKEN=000000000:AAAAAAAAAA # Replace with actual

# Get from @userinfobot on Telegram
ALLOWED_CHAT_ID=123456 #，0002,0003 so on

# --- Connection Mode ---
# How the bot connects to the environment where the AI agent runs.
# Options:
#   ssh    (in WSL or macOS connecting to HPC using SSH)
#   wsl    (I am in WSL and connect to WSL)
#   local  (in local connect to local, e.g., macOS/Linux)
CONNECTION_MODE=wsl

# --- SSH ---
# Must match a Host entry in your ~/.ssh/config if CONNECTION_MODE=ssh
SSH_HOST=

# --- Agent Paths ---
# Full path to the AI agent binary on the HPC
OPENCODE_PATH=~/.opencode/bin/opencode

# Default working directory on the HPC
HPC_WORKDIR=~/

# Default AI model (Select depending on your subscription)
DEFAULT_MODEL=opencode/minimax-m2.5-free

# --- Environment Setup (REQUIRED if your target uses environment modules) ---
# Shell commands to run on the target before starting the AI agent.
# These are executed in a non-login bash shell, so login-time module setup
# does NOT happen automatically -- you must specify it here.
#
# Find your correct values by running `module list` in a live session,
# then copy the relevant module load commands.
#
# Examples:
#
#   Imperial College London (cx3):
#   SETUP_CMD=module purge && module load tools/dev && module load nodejs/20.13.1-GCCcore-13.3.0
#
#   Generic Lmod cluster (most universities):
#   SETUP_CMD=module load nodejs
#
#   Conda/mamba environment (no modules):
#   SETUP_CMD=source ~/miniconda3/etc/profile.d/conda.sh && conda activate myenv
#
#   Node installed globally, no setup needed:
#   SETUP_CMD=
#
SETUP_CMD=

# --- rclone Integration (optional) ---
# Destination for /upload rclone transfer.
# Format: remote_name:path  (as configured in `rclone config` on target)
#
# Examples:
#   gdrive:HPC-Results          (Google Drive folder)
#   onedrive:Projects/HPC       (OneDrive)
#   s3:mybucket/results         (S3-compatible)
#   sharepoint:Documents/HPC    (SharePoint)
#
RCLONE_DEST=

# --- OpenCode Session Database (optional) ---
# Path to OpenCode's SQLite database ON THE TARGET (used by the chat viewer tool).
# Default is correct for most OpenCode installs -- only change if you customised
# the OpenCode data directory.
# OC_DB_PATH=~/.local/share/opencode/opencode.db

# --- Session Persistence (optional) ---
# File on the RELAY MACHINE where active session IDs are stored between messages.
# SESSIONS_FILE=~/.hpc_relay_sessions.json


# --- Workspace Separation (optional but recommended) ---
# Explicit mapping per Telegram chat_id -> isolated workspace/session/task files.
# JSON format example:
# CHANNEL_WORKSPACES={"123456":{"name":"AA","workdir":"~/workspace_AA","allowed_users":[123456]},"-000000":{"name":"group_shared","workdir":"~/workspace_shared"}}
# If name is set, session/task files become:
#   hpc_relay_sessions_<name>.json
#   hpc_relay_tasks_<name>.json
CHANNEL_WORKSPACES=
# Auto-create isolated workspace namespace by chat_id when no explicit mapping exists.
# 0 = disabled (default), 1 = enabled
AUTO_WORKSPACE_PER_CHAT=0
# Prefix for auto workspace names: <prefix>_<chat_id>
AUTO_WORKSPACE_PREFIX=chat