# mercury-agent

> Soul-driven AI agent with permission-hardened tools, token budgets, and multi-channel access. Runs 24/7 from CLI or Telegram.

- **URL**: https://www.freshcrate.ai/projects/mercury-agent
- **Author**: cosmicstack-labs
- **Category**: Security
- **Latest version**: `v1.1.12` (2026-06-01)
- **License**: MIT
- **Source**: https://github.com/cosmicstack-labs/mercury-agent
- **Homepage**: https://mercury.cosmicstack.org/
- **Language**: TypeScript
- **GitHub**: 314 stars, 41 forks
- **Registry**: github (`cosmicstack-labs/mercury-agent`)
- **Tags**: `ai-agent`, `ai-assistant`, `llm`, `typescript`

## Description

Soul-driven AI agent with permission-hardened tools, token budgets, and multi-channel access. Runs 24/7 from CLI or Telegram.

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `v1.1.12` | 2026-06-01 | High | # Release v1.1.12  ## ☿ Mercury Agent v1.1.12 — Daemon hotfix  Hotfix on top of [v1.1.11](https://github.com/cosmicstack-labs/mercury-agent/releases/tag/v1.1.11). The standalone single-file binaries introduced in 1.1.11 could not start in the background — which meant Telegram never came online for anyone who installed Mercury via the one-line installer (the recommended path for web servers).  ### What Was Broken  `src/cli/daemon.ts` spawned the daemon child as:  ``` spawn(process.execPath, [proc |
| `v1.1.11` | 2026-05-31 | High | # Release v1.1.11  ## ☿ Mercury Agent v1.1.11  **Token Saver Mode, full Skill System, and standalone binaries.**  The biggest release since the 1.1.x line began — Mercury now ships as a single executable on every major OS, learns new tricks via user-defined skills, and gives you a live status bar with token usage at the bottom of every session.  ### What's New  - **Token Saver Mode** (#69) — opt-in mode that aggressively trims session context so long-running agents don't bleed tokens. Pairs with |
| `v1.1.9` | 2026-05-19 | High | Release `1.1.9` introduces the **Mercury Web Dashboard** — a full React SPA at `localhost:6174` — alongside a persistent **Kanban board system**, an in-browser **Workspace IDE** with Git and AI commit messages, a **dual-layer (conscious + subconscious) Second Brain**, intelligent **skill batching**, and a cross-platform build pipeline.  > **Note:** Version `1.1.8` was published briefly and then unpublished before reaching wide distribution due to a dependency-tree issue (a transitive `next` dep |
| `v1.1.6` | 2026-05-06 | High | Mercury v1.1.6 is a substantial CLI/TUI and workflow upgrade focused on reliability, long-running task handling, coding workspace ergonomics, and clearer operator controls.  ## What’s happening in this release This release improves how Mercury behaves as a daily driver in terminal-first workflows: - better startup + input handling stability - IDE-like workspace flow for coding sessions - stronger background execution for long tasks/sub-agents - richer Spotify control surface in CLI - session-lev |
| `v1.1.5` | 2026-05-02 | High | ## What's Changed  ### Fixed: Onboarding no longer blocks users without Ollama  The onboarding flow had a critical UX problem: if a user didn't have Ollama running locally or an API key handy, they'd get stuck in infinite loops with no way to skip. This release makes onboarding smooth and forgiving.  **Key changes:**  1. **Ollama Local is now skippable** — If Ollama isn't running, you can skip it entirely or manually enter a model name. No more infinite retry loops.  2. **All provider setups all |
| `v1.1.0` | 2026-04-26 | High | ## What's Changed  ### DeepSeek v4 Compatibility - **New dedicated DeepSeek provider** (`@ai-sdk/deepseek`) — replaces the OpenAI-compatible workaround with a proper SDK integration that correctly handles DeepSeek's reasoning mode (`deepseek-reasoner`). - **Thinking mode support** — DeepSeek reasoner models now pass `thinking: { type: 'enabled' }` via `providerOptions`, ensuring `reasoning_content` is included in the response and round-tripped back to the API (fixes the `The reasoning_content in |
| `v0.4.0` | 2026-04-22 | High | ## ☿ Mercury Agent v0.4.0  **Persistent working directory, Ollama support, Telegram messaging, and more.**  ### Highlights  - **`cd` tool** — Change directories persistently. All subsequent file, shell, and git operations use the new working directory. No more lost `cd` between commands. - **Relative path support** — All 8 filesystem tools and all 6 git tools now resolve relative paths against the current working directory instead of `process.cwd()`. - **`run_command` learns `cd`** — Running `cd |
| `v0.3.4` | 2026-04-21 | High | ## Changes  ### Simplified GitHub Setup (3 steps instead of 4)  - **Removed the email field** — `Co-authored-by: Mercury <mercury@cosmicstack.org>` is now the default. No need to ask users for an email. - **Default co-author email** — `mercury@cosmicstack.org` is hardcoded as the default in config. Users can override via `GITHUB_EMAIL` env var if they want, but 99% won't need to. - **Numbered prompts** — Setup now shows clear step numbers (1. username, 2. PAT, 3. default repo) - **URL parsing fo |
| `v0.3.2` | 2026-04-21 | High | ## Bug Fixes  ### Critical: GitHub tools now actually make API calls  The previous implementation had three bugs causing the LLM to fabricate GitHub API responses:  1. **`getCurrentRepo()` was required but failed in daemon/Telegram mode** — When Mercury isn't running inside a git repo directory (daemon mode, Telegram), the auto-detection of `owner/repo` from `git remote` failed silently. The LLM then fabricated success responses instead of reporting errors.  2. **`github_api` used `checkShellCom |
| `v0.3.1` | 2026-04-21 | High | ## Bug Fixes  - **GITHUB_TOKEN now loads from `~/.mercury/.env`** — previously, dotenv only read from the project directory, so tokens saved during `mercury doctor` were never picked up. Now both `.env` locations are loaded. - **GitHub tools now appear in the LLM's system prompt** — when `GITHUB_TOKEN` is configured, the agent tells the LLM it can create PRs, review PRs, manage issues, and use the GitHub API. Without this, the LLM didn't know GitHub tools existed.  **Full Changelog**: https://gi |

## Citation

- HTML: https://www.freshcrate.ai/projects/mercury-agent
- Markdown: https://www.freshcrate.ai/projects/mercury-agent.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/mercury-agent/deps

_Generated by freshcrate.ai. Indexes github releases for AI-agent ecosystem packages._