# @peteretelej/ai-chat

> Local-first AI chat system routing messages to agents in tmux sessions

Latest version **0.1.1** (published 2026-09-23) · Apache-2.0 license · 0 weekly downloads

## Install

```sh
npm install @peteretelej/ai-chat
pnpm add @peteretelej/ai-chat
yarn add @peteretelej/ai-chat
bun add @peteretelej/ai-chat
```

Provides the command `ai-chat`.

## Health

**Score 55/100 (C)** — status: active.

Positive: no vulnerabilities; recently updated; high maintenance score.

Warnings: low downloads; no types; no esm support; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.1.1 |
| Published | 2026-09-23 |
| First published | 2026-09-23 |
| Weekly downloads | 0 |
| License | Apache-2.0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 6.4 KB |
| Known vulnerabilities | 0 |
| Install scripts | yes |
| Maintainers | peteretelej |
| Keywords | mcp, ai, chat, telegram, tmux, opencode |

## Links

- npm: https://www.npmjs.com/package/@peteretelej/ai-chat
- Repository: https://github.com/peteretelej/ai-chat
- Homepage: https://github.com/peteretelej/ai-chat#readme
- Issues: https://github.com/peteretelej/ai-chat/issues
- npm.io page: https://npm.io/package/@peteretelej/ai-chat

## Alternatives

- [@expo/fingerprint](https://npm.io/package/@expo/fingerprint.md) — 6.2M weekly downloads
- [@azure/monitor-opentelemetry-exporter](https://npm.io/package/@azure/monitor-opentelemetry-exporter.md) — 850.0K weekly downloads
- [@azure/monitor-opentelemetry](https://npm.io/package/@azure/monitor-opentelemetry.md) — 624.0K weekly downloads
- [@posthog/ai](https://npm.io/package/@posthog/ai.md) — 423.3K weekly downloads
- [fakefilter](https://npm.io/package/fakefilter.md) — 63.9K weekly downloads

## Recent versions

- 0.1.1 (latest) — 2026-09-23
- 0.1.0 — 2026-09-23

## README

# ai-chat

Chat with & control AI Agents via telegram, chat UI & voice.

> **Note:** Claude Code will not be supported (first class support for OpenCode, Copilot, Codex intended via CLI)

## Running

- Start the Telegram bot with `go run ./cmd/ai-chat start --config ./config.json`
- Run the in-process regression suite with `go run ./cmd/ai-chat test`
- Run one named regression with `go run ./cmd/ai-chat test --scenario "Session switching regression"`
- Run the explicit Telegram acceptance path with `go run ./cmd/ai-chat test --scenario telegram-acceptance --config ./config.json`

## Validation

- Final refactor validation is `go test ./...`
- Then run `./scripts/pre-push`
- Then run one explicit `telegram-acceptance` pass against a real Telegram bot/chat configuration

## Telegram Acceptance

- `telegram-acceptance` is opt-in and is not part of normal `go test` or default `ai-chat test` runs
- By default it uses `telegram.bot_token`
- You can override the bot with `telegram.acceptance_bot_token`
- You should set `telegram.acceptance_chat_id` to the real chat to validate
- If you omit `telegram.acceptance_chat_id`, the command only falls back when `telegram.allowed_users` contains exactly one direct-chat user ID

## Runtime Notes

- The in-process test harness now boots the same store, router, session manager, watcher, and outbound response flow used by `start`
- Telegram remains a transport/rendering adapter on top of router and session-manager behavior

---
_Source: https://npm.io/package/@peteretelej/ai-chat · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._