Negotium — AI skill for Claude Code
Self-hosted local AI agent runtime — run Claude Code, Codex, or Maestro with shared memory, skills, vault, and cron schedules, reachable from Terminal, Telegram, and Otium.
How to install Negotium
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open maestrojeong/negotium and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Negotium does
Self-hosted local AI agent runtime — run Claude Code, Codex, or Maestro with shared memory, skills, vault, and cron schedules, reachable from Terminal, Telegram, and Otium.
Alternatives in AI
- Invisible Dots — Open-source, self-hosted alternative to OpenAI Dots, Meta Muse, Grok Bot, Manus Cue and Claude Cowork 31.8k ★
- Hindsight — State-of-the-art long-term memory for AI agents by Vectorize 6.7k ★
- Dinotty — Multi-device terminal server for AI coding agents 643 ★
README
Negotium
One machine, one Negotium runtime — reachable from Terminal, Telegram, and multiple Otium workspaces at once.
Run Claude, Codex, or Maestro with local tools, memory, and schedules.

*Negotium* is Latin for “work” — literally *nec otium*, the absence of leisure. Your machines do the negotium so you can keep the otium.
The Negotium Node
A Negotium **node** is the durable runtime running on one machine — it owns topics, provider sessions, queues, tools, workspaces, and local state. It is not a runtime that belongs to a single surface. Terminal, Telegram, and any number of Otium workspaces (local or remote) can all reach the same node.
What's shared across every surface connected to a node is the runtime layer:
- memory and wiki — knowledge persists across topics and surfaces
- skills — reusable instructions available to every topic
- the vault — one encrypted secret store per node, referenced as
{{KEY}} - tools and MCP servers — browser, shell, file, and custom tools
- Cron schedules — durable, restarts survive, missed runs coalesced
What's *not* shared is scoped on purpose: a **topic** belongs permanently to one surface (`terminal` | `telegram` | `otium`) chosen when it's created, and an Otium-surface topic further belongs to the one workspace it was created in — so
Related Skills
Mnemon
Self-hosted, cross-device long-term memory for AI agents via MCP — one vault shared across any MCP client (Cla
Opendray
Self-hosted gateway for Claude Code, Codex, Antigravity, Grok Build, OpenCode. Run AI coding agents on your ow
Matrixclaw
Always-on local AI assistant and AI coding agent runtime in Go. OpenClaw, Claude Code, Codex, and OpenCode alt
Kronos Agent OS
Kronos Agent OS (KAOS): self-hosted runtime for durable AI agents with memory, skills, MCP tools, automations,
Ella Claude Code AI Agent
Autonomous AI chief-of-staff agent built on Claude Code. Multi-tenant template — blank Ubuntu VPS to a Telegra
Memento
A shared brain for your AI coding tools — collects conversations, plans and memory from Claude Code / Cursor /
Related Agents
Infra Vault
Secrets specialist. Machine identity, env injection, rotations, break-glass for a self-hosted secrets vault (I
Schedules
Configure manual or cron-based Agent runs and inspect each Schedule trigger through SandBase Sessions.
Bench Runner
Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scrip