Theme
AI Resources
Mercury Agent
Mercury Agent is a public Cosmic Stack project for running a personal AI agent from the terminal, a local web dashboard, or messaging channels, with provider choices, tools, skills, persistent memory, scheduled work, and background operation.
Its official materials separate Ask Me from Allow All permission modes, store personality in user-editable Markdown files, add daily token budgeting, and keep Second Brain memory in a local SQLite database. Version 1.1.13 is available through npm and standalone binaries. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
A personal agent runtime
Mercury combines a terminal interface, local web dashboard, messaging channels, model-provider choices, tools, skills, memory, scheduling, and background service operation in one public TypeScript project.
Why it stands out
Permissions, memory, and budgets stay visible
The project exposes session permission modes, folder scopes, blocked shell patterns, local structured memory controls, user-owned personality files, token budgets, and loop detection instead of hiding those choices behind one assistant interface.
Availability
npm and standalone install paths
The official installation guide lists npm, Bun, pnpm, Yarn, and standalone binary paths for macOS, Linux, Windows, Termux, and lightweight devices. The npm package requires Node.js 20 or newer.
Why it matters
What makes it useful
Mercury is useful when a personal agent has to outlast one terminal session. It can run as a background service, keep its structured memory in a local SQLite database, and use personality Markdown files that the user can edit, giving the reader concrete files and controls to preserve as models or providers change.
What to know
Where it fits
Read Mercury as a configurable personal-agent runtime rather than a finished consumer chatbot. It is most relevant to technically comfortable readers comparing always-on assistants, local memory, provider fallback, messaging access, skills, scheduled work, and permission boundaries.
Notable points
What stands out
The official site, repository, package metadata, and release page identify v1.1.13 as the current stable line. The public materials cover the CLI and local dashboard, Telegram, Discord, Slack, and Signal channels, Second Brain memory, skills, multi-agent work, provider choices, token budgets, scheduling, permissions, and service installation.
Before using
What to review
Whether Ask Me or Allow All matches the task. The permissions guide says scheduled tasks run in Allow All mode, so review scheduled work and tool scopes before leaving the agent unattended.
Which model providers, API keys or OAuth accounts, messaging tokens, repositories, folders, shell commands, and external services the setup would reach.
Which personal facts the enabled Second Brain may extract, and how its local SQLite file, pause, search, edit, clear, backup, and file-permission choices should be handled.
How the background service, local dashboard, messaging access, logs, and auto-restart behavior fit the security and maintenance needs of the machine running it.
The current package version, platform notes, dependencies, permission defaults, and project documentation before using it with private or important work.
Reader fit
Who may find it relevant
Readers who want a personal agent they can configure, inspect, and keep running on their own machine.
People comparing how agent projects handle memory, provider choice, permissions, skills, budgets, schedules, and messaging access.
Builders who want a public TypeScript codebase plus npm and standalone installation routes.
Less relevant for someone who wants a hosted assistant with no local setup, service management, provider configuration, or permission decisions.
Editorial note
Why LifeHubber lists it
Mercury puts three practical parts of a personal agent in one public project: what it may do, what it remembers, and how much token use it can consume. That makes it a useful comparison point for an always-on assistant without treating convenience as the only measure.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Keep the agent portable after the first setup.
An always-on assistant becomes more useful as it remembers more, which makes its files, permission boundaries, and fallback path worth planning early.
More in AI Agents
Keep browsing this category
A few more places to continue in ai agents.
Agent-Reach
Panniantong/Agent-Reach
A CLI and channel-routing layer for command-capable agents, with documented paths for web pages, YouTube, RSS, GitHub, Twitter/X, Reddit, Bilibili, Xiaohongshu, Facebook, Instagram, LinkedIn, V2EX, Xueqiu, podcasts, and Exa search, plus doctor checks and safe/dry-run install review.
AIPOCH Medical Research Skills
aipoch/medical-research-skills
A curated library of medical research agent skills designed to support evidence review, protocol design, data analysis, and academic writing workflows.
Claude Code Game Studios
Donchitos/Claude-Code-Game-Studios
A multi-agent game-development studio system for Claude Code, organized around specialized agents, workflow skills, hooks, rules, and templates.
Related in LifeHubber
Keep the thread going
Follow the next layer with AI Resources for AI projects with original links and practical caveats, AI Guides for decision habits for messy AI choices, AI Access for free and low-cost ways to compare AI model access, AI Ballot for a clearer view of what readers are leaning toward, and AI Radar for AI stories that deserve a second look.