claude-telegram-bot 0.3.0 → 0.3.1

package/README.ko.md

@@ -68,11 +68,10 @@ OpenClaw처럼 웹 UI까지 갖춘 구성을 써봤다면, 이 프로젝트는
 **npx로 바로 실행**
 
 ```sh
-npx claude-telegram-bot init              # 현재 폴더에 config.json 생성
-npx claude-telegram-bot init mybot.json   # 파일명 직접 지정도 가능
+npx claude-telegram-bot init              # 현재 폴더에 mybot.json 생성
+npx claude-telegram-bot init myapp.json   # 파일명 직접 지정도 가능
 # 설정 편집 (token, projectDir 등)
-npx claude-telegram-bot                   # config.json 으로 실행
-npx claude-telegram-bot mybot.json        # 또는 경로를 직접 전달
+npx claude-telegram-bot                   # mybot.json 으로 실행 (없으면 config.json 폴백)
 ```
 
 **전역 설치 (상시 가동에 권장)**
@@ -80,8 +79,8 @@ npx claude-telegram-bot mybot.json        # 또는 경로를 직접 전달
 ```sh
 npm i -g claude-telegram-bot
 
-claude-telegram-bot init ~/botconfigs/myproj              # config.json 생성
-claude-telegram-bot init ~/botconfigs/myproj/mybot.json   # 또는 파일명 지정
+claude-telegram-bot init ~/botconfigs/myproj              # mybot.json 생성
+claude-telegram-bot init ~/botconfigs/myproj/myapp.json   # 또는 파일명 지정
 # 설정 편집
 claude-telegram-bot ~/botconfigs/myproj/mybot.json
 ```
@@ -90,7 +89,7 @@ claude-telegram-bot ~/botconfigs/myproj/mybot.json
 
 ## 설정
 
-`config.json`의 키는 다음과 같습니다.
+`mybot.json`(또는 사용 중인 config 파일)의 키는 다음과 같습니다.
 
 | 키 | 설명 |
 |---|---|

package/README.md

@@ -118,11 +118,10 @@ Prerequisites: **Node 18+** and the **`claude` CLI installed and authenticated**
 **Option A — npx (no install)**
 
 ```sh
-npx claude-telegram-bot init             # writes ./config.json
-npx claude-telegram-bot init mybot.json  # or pick your own filename
+npx claude-telegram-bot init             # writes ./mybot.json
+npx claude-telegram-bot init myapp.json  # or pick your own filename
 # edit the config (token, projectDir, …)
-npx claude-telegram-bot                  # runs ./config.json
-npx claude-telegram-bot mybot.json       # or pass the path directly
+npx claude-telegram-bot                  # runs ./mybot.json (falls back to config.json)
 ```
 
 **Option B — global install (recommended for an always-on daemon)**
@@ -130,8 +129,8 @@ npx claude-telegram-bot mybot.json       # or pass the path directly
 ```sh
 npm i -g claude-telegram-bot
 
-claude-telegram-bot init ~/botconfigs/myproj           # writes ~/botconfigs/myproj/config.json
-claude-telegram-bot init ~/botconfigs/myproj/mybot.json  # or a custom filename
+claude-telegram-bot init ~/botconfigs/myproj             # writes ~/botconfigs/myproj/mybot.json
+claude-telegram-bot init ~/botconfigs/myproj/myapp.json  # or a custom filename
 # edit the config (token, projectDir, …)
 claude-telegram-bot ~/botconfigs/myproj/mybot.json
 ```
@@ -152,7 +151,7 @@ Run several projects/personas by making one config file each and passing its pat
 leave `allowedChatId` empty for now.
 
 **2) Find your chatId and lock the bot to it** — Start the bot (`claude-telegram-bot …`), send it any
-message in Telegram; it replies with this chat's `chatId`. Put that number into `config.json`
+message in Telegram; it replies with this chat's `chatId`. Put that number into `mybot.json`
 `allowedChatId` and restart. Now only you can use it. (See [Security](#security) — this is your only
 auth layer.)
 
@@ -175,18 +174,18 @@ Commands: `/new` (reset context / new session) · `/stop` (stop current task; `-
 
 **4) Keep it always on (optional)** — see [Always-on with launchd](#always-on-with-launchd-macos).
 
-> **From source** (for hacking on the bot): clone the repo, `cp config.example.json config.json`,
-> then `node bot.mjs [config.json]`. Same behavior as the CLI.
+> **From source** (for hacking on the bot): clone the repo, `cp config.example.json mybot.json`,
+> then `node bot.mjs [mybot.json]`. Same behavior as the CLI.
 
 ---
 
 ## Configuration
 
 ```sh
-cp config.example.json config.json
+cp config.example.json mybot.json
 ```
 
-Edit `config.json`:
+Edit `mybot.json`:
 
 | Key | Description |
 |---|---|
@@ -273,7 +272,7 @@ Config-defined jobs still require a restart to change; only chat-added jobs are
 
 The code is project-agnostic: make **one config file per project** and run several at once.
 
-- Run: `node bot.mjs /absolute/path/to/project.config.json` (no arg → `./config.json`)
+- Run: `node bot.mjs /absolute/path/to/project.config.json` (no arg → `./mybot.json`, fallback `./config.json`)
 - `state.json` and `attachments/` live in the **config file's folder**, so projects don't mix.
 - **Note**: Telegram allows only one poller per token → each project needs its **own BotFather
   token**.
@@ -299,7 +298,7 @@ One codebase, **a separate config file per role**.
   shell-using bot (`bypassPermissions`) to **just one** to avoid concurrent-edit conflicts. For
   read/plan-only, use `plan`.
 - **Session isolation**: the `state` filename is derived from the config name
-  (`config.json` → `state.json`, `dev.config.json` → `dev.config.state.json`), so multiple configs
+  (`mybot.json` → `mybot.state.json`, `dev.config.json` → `dev.config.state.json`), so multiple configs
   in one folder don't share context.
 - **One token per bot**: each bot needs its own BotFather token (`allowedChatId` can be the same).
 

package/bot.mjs

@@ -58,7 +58,7 @@ Requires: the claude CLI installed and authenticated on the host.`);
   }
   if (a === "init") {
     const arg = process.argv[3];
-    const target = arg?.endsWith(".json") ? resolve(arg) : join(arg || process.cwd(), "config.json");
+    const target = arg?.endsWith(".json") ? resolve(arg) : join(arg || process.cwd(), "mybot.json");
     if (existsSync(target)) {
       console.error(`Already exists: ${target}`);
       process.exit(1);
@@ -71,8 +71,9 @@ Requires: the claude CLI installed and authenticated on the host.`);
 
 // Config path via arg or BOT_CONFIG env so one shared codebase can drive many
 // projects; state + attachments live next to that config, keeping projects
-// isolated. Falls back to ./config.json for the single-project setup.
-const CONFIG_PATH = process.argv[2] || process.env.BOT_CONFIG || join(HERE, "config.json");
+// isolated. Defaults to mybot.json, falls back to config.json for existing setups.
+const _defaultCfg = existsSync(join(HERE, "mybot.json")) ? join(HERE, "mybot.json") : join(HERE, "config.json");
+const CONFIG_PATH = process.argv[2] || process.env.BOT_CONFIG || _defaultCfg;
 const DATA_DIR = dirname(CONFIG_PATH);
 // 데이터(state·attachments)는 config 폴더 아래 숨김 폴더 .claude-bot/ 에 모은다.
 // state 파일명은 config 이름에서 파생 → 여러 페르소나 config 가 한 .claude-bot/ 를 공유해도 안 섞임

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-telegram-bot",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Drive Claude Code from Telegram — messages run headless `claude -p` in a project dir and replies come back to the chat. Zero dependencies.",
   "type": "module",
   "bin": {