HyperChat

Community

A local AI agent platform where configuration is code and tools come in through MCP

★ 707 Stars Category · Dev Tools Very popular

39FMRS · D

HyperChat is a local-first AI chat and agent platform that organizes agents, memory, and MCP services around a configuration-as-code model, with two entry points: a Web multi-workspace mode and a CLI agent-first mode. The README is detailed about environment-variable layering, agent configuration, and custom commands, but says nothing about specific MCP tools, transports, or client setup, and the source contains no server manifest (not cached). The license is marked NOASSERTION in the source and the README only points to a LICENSE file, so confirm the terms before use.

Reliability

7/20

Security and permissions

6/20

Maintenance

9/20

Documentation

9/20

Setup experience

8/20

Read the FMRS scoring method →

HyperChat is a local AI agent platform (its Chinese README describes it as pioneering an "AI as Code" idea) that uses APIs from various LLMs for its chat experience and implements productivity tools through the MCP protocol. It emphasizes full localization: data stays on the machine, and configuration lives as files under a .hyperchat/ directory that travels with the project and can be version-controlled with Git. The project uses a two-tier architecture: a Web front end acting as a multi-workspace collaboration hub, and a CLI front end optimized for agent-first interaction. Agents support a memory file (memory.md), MCP services declared in agent.yaml, and Markdown-template-driven custom commands such as /bug-fix and /review. The README notes that HyperChat 1.0 was a fully hand-written project and is being migrated to 2.0. No MCP tool inventory, transport details, or client connection config examples are provided in the source.

Setup

The README offers two paths: 1) Install globally with npm install -g @dadigua/hyperchat, or run it directly with npx -y @dadigua/hyperchat. 2) Develop from source: git clone https://github.com/BigSweetPotatoStudio/HyperChat.git, then npm install, followed by npm install inside packages/electron and packages/web, and finally npm run dev. Before use, configure environment variables such as HyperChat_API_KEY, HyperChat_API_URL, HyperChat_AI_Provider (e.g. openai/claude/gemini/kimi/qwen) and HyperChat_AI_Model (e.g. gpt-4o). Start the Web UI with hyperchat serve (default http://localhost:16100), or invoke an agent directly with hyperchat agent <name> "...".

Fit and risk

Best for

Developers who want AI configuration stored locally and managed in Git
Users who need to reuse a personal agent across projects while keeping per-project context
Users who want agents to act on local resources such as the file system through MCP
Engineering teams that need a command-line entry point for automation

Not for

Users who just want a hosted, zero-configuration cloud chat service
Users who require official commercial support or SLAs from the project maintainers
Users looking for a ready-made MCP tool list and client setup config, which the README does not provide

Required permissions

Local file system read/write: the README states agents can operate on the local file system directly through the MCP protocol
Reading the project's .hyperchat/ configuration, agent memory, and chat logs
Reading environment variables and .env files (API keys, service port, Web access password)
Starting a local Web service that listens on a port (default 16100)
Calling external LLM provider API endpoints

Risks and side effects

Once an agent is granted file-system or terminal MCP tools, it may modify local files, possibly without confirmation; the isConfirmCallTool setting in agent.yaml affects whether calls are confirmed
Configuration, agent memory, and chat logs are stored as plain local files, so committing them to Git or sharing the directory can leak sensitive information
Credentials such as API keys live in environment variables or .env files and can be committed by mistake or read by other local processes
If HYPERCHAT_WEB_PASSWORD is not set, the local Web service may be reachable by other processes or machines on the same network
Custom command templates send the referenced @ file contents to the configured LLM provider
The README states the project is for learning and exchange only and describes no security guarantees or audit mechanisms

Troubleshooting

Verify HyperChat_API_KEY, HyperChat_API_URL, HyperChat_AI_Provider, and HyperChat_AI_Model; configuration follows a 5-level priority (defaults < process.env < global .env < workspace .env < CLI arguments), so check whether a higher layer overrides your setting
If the Web UI is unreachable, check HYPERCHAT_PORT (default 16100) and HYPERCHAT_HOST, and whether an access password was configured
If an agent is missing, run hyperchat agent list to see agents available globally and in the workspace
If an agent cannot use an MCP tool, check whether allowMCPs in agent.yaml includes that service and whether the workspace mcp.json service pool defines it
If a custom command does not trigger, confirm it is a .md file under the agent's commands/ directory and invoked with a / prefix
For more detail, use --verbose or adjust HYPERCHAT_LOG_LEVEL

Use cases

Defining project-specific agents, memory, and MCP service pools in a project-local .hyperchat/ directory

Using the CLI in agent-first mode for quick conversations or for embedding into scripts and CI/CD flows

Managing several project workspaces, agent sets, and chat histories side by side in the Web multi-workspace UI

Reusing fixed prompt workflows through Markdown-defined slash commands

Analyzing or comparing several files at once by referencing multiple @ file paths

Related MCP servers

Compare with other MCP servers