Ethos

Most AIs try to be good at everything. Ethos gives you a team — each one really good at just one thing.

Ethos builds AI agents that have an identity — not a prompt.

You wouldn't hire one person to be your engineer and your researcher. Why pretend an AI can? Build your own personality with Ethos.

Five ship by default — pick one, or build your own:

• engineer — writes working code; tests what ships; refuses to pad.
• researcher — finds primary sources; flags uncertainty; shows the reasoning.
• reviewer — finds real problems; separates blocking from suggestion; does not soften.
• coach — asks one question at a time; helps you think, not for you.
• operator — dry-runs before destructive action; confirms; documents what happened.

Each runs across CLI, Telegram, Discord, Slack, and Email — same identity, same memory, same boundary, every surface. Teams are the other half: named personalities that coordinate through visible artifacts — a kanban board, a shared topic file, an audit trail — not behind one chatbot voice. The user can see who decided what.

Quick install

Standard install (Node 24+, Linux / macOS / WSL2)

npm i -g @ethosagent/cli
ethos setup           # provider + API key + personality selection (interactive)
ethos chat            # interactive REPL — talk to your agent

ethos setup writes ~/.ethos/config.yaml and stores credentials in ~/.ethos/secrets/<ref> with chmod 0600.

Production install (always-on box: VPS, mini PC, Raspberry Pi 4+, Mac mini)

npm i -g @ethosagent/cli pm2
ethos setup
curl -O https://ethosagent.ai/ecosystem.config.js
pm2 start ecosystem.config.js && pm2 save && pm2 startup

ethos run-all spawns the gateway (all configured bot adapters + cron) and the web dashboard under one supervisor. PM2 keeps it alive across reboots and restarts on crash. Sizing, log rotation, upgrade flow, and troubleshooting: Deploy in production →.

Windows note

Native Windows is not a primary target. Use WSL2 (Ubuntu 22.04 or 24.04). Node 24+ inside the WSL distro; ~/.ethos/ lives in the Linux home, not the Windows mount.

Installing the desktop app on macOS

Since the app is unsigned and unnotarized, macOS will block it on first open:

"Ethos" cannot be opened because Apple cannot verify it is free from malware.

Option A — right-click method (easier):

1. Open the .dmg and drag Ethos to Applications
2. Right-click Ethos.app in your Applications folder
3. Click Open
4. Click Open again in the dialog that appears
5. The app opens. This only needs to be done once.

Option B — terminal (if Option A doesn't work on macOS 15+):

xattr -dr com.apple.quarantine /Applications/Ethos.app

Getting started

ethos setup                       # first-time config — provider, keys, default personality
ethos chat                        # interactive REPL against the default personality
ethos chat --personality engineer # one-off with a specific personality

ethos personality list            # five built-ins + anything you've added
ethos personality show engineer   # character sheet: identity, tools, skills, model, fs_reach
ethos personality create my-team  # scaffold ~/.ethos/personalities/my-team/

ethos gateway                     # run all configured bot adapters (Telegram + Slack + ...)
ethos run-all                     # supervisor: gateway + web dashboard, one command

ethos sessions list               # browse past conversations
ethos sessions show <id>          # full transcript + tool calls

ethos memory show                 # MEMORY.md + USER.md for the active personality
ethos memory add "We use ESM, never CJS"   # durable note — survives sessions

ethos secrets list                # which credentials are configured (refs only, never values)
ethos secrets set providers/anthropic/apiKey   # set or rotate — chmod 0600 enforced

ethos cron add daily-digest "0 8 * * *" "summarize what you learned yesterday"
ethos skills install steipete/slack   # any clawhub skill, no fork required
ethos claw migrate --dry-run      # one-step from an existing OpenClaw install

ethos doctor                      # boot-time sanity check — config, keys, perms, providers

Full subcommand reference: CLI reference →.

CLI vs chat surfaces

The same actions are available on every surface. Pick the one the conversation lives on; sessions and memory follow the personality, not the channel.

Bots are bound to a personality at config time. The default binding locks /personality switching off so external users can't reroute the bot — flip allowSlashSwitch: true if you want them to.

Documentation

Migrating from OpenClaw or Hermes

ethos claw migrate carries memory, skills, platform tokens, and provider keys from an existing OpenClaw or Hermes install into the Ethos layout. Dry-run first:

ethos claw migrate --dry-run     # preview the plan; touches nothing
ethos claw migrate               # apply

What moves cleanly:

• MEMORY.md and USER.md → the new personality's memory scope, identical semantics.
• SOUL.md (OpenClaw) → a migrated personality with SOUL.md derived from it; built-in matches resolve automatically (engineer.md lands on the built-in engineer, etc.).
• Platform tokens (Telegram bot tokens, Slack app credentials, Discord tokens) → the new SecretsResolver with chmod 0600, referenced from config.yaml as ${secrets:slack/<bot>/botToken}.
• Provider API keys → ~/.ethos/secrets/providers/<provider>/apiKey.
• Skills directory → unchanged path semantics; OpenClaw-compat parses SKILL.md frontmatter, env substitutions, and OS gates, so existing clawhub skills install and run without modification.

Idempotent — safe to re-run. What does not move (and why is documented in the migration guide):

• Anything that was inline plaintext in config.yaml migrates to the secrets resolver; the config file gets rewritten to use ${secrets:...} refs.
• Personality boundary settings (fs_reach, safety.network.allow) are added on migration with safe defaults; review them before the first bot run.

Full migration reference: Migrate from OpenClaw →.

You can also stay on your existing setup and install Ethos-native skills into OpenClaw or Hermes — every Ethos skill is SKILL.md-shaped and runs unmodified. The migration command is for operators who want the full personality-is-architecture model.

Contributing

Three documents are mandatory reading before any non-trivial change:

Local setup:

git clone https://github.com/MiteshSharma/ethos
cd ethos
make prepare    # pnpm install + git hooks
make check      # typecheck + lint + test (mirror of CI)
make dev        # run the CLI from source

Repo layout:

packages/    @ethosagent/{types, core, plugin-sdk, plugin-contract, ...}
extensions/  llm-*, session-*, memory-*, platform-*, tools-*, gateway, ...
apps/        ethos (CLI), tui, vscode-extension, web, web-api
docs/        Docusaurus site — content/, plugins/, scripts/
plan/        Architecture notes, phase plans, completed plans

The CLI binary entry is apps/ethos/src/index.ts. Every extension point is a typed interface in packages/types/src/index.ts, injected into AgentLoop at construction. Core never imports concrete implementations.

Open an issue before non-trivial changes — alignment is cheaper than rework. Look for good-first-issue to find a starter task. Plugin authors: the plugin SDK quickstart shows how to publish a tool, hook, channel adapter, or memory provider as a standalone npm package.

Community

• Issues: github.com/MiteshSharma/ethos/issues — bug reports, feature requests, questions
• Docs site: ethosagent.ai/docs
• Plugin examples: examples/plugins/ — hello, personality, safety-adapter (use as templates)
• OpenClaw skill catalog: any clawhub skill installs unchanged via ethos skills install <slug>
• MCP clients: Ethos is consumable from Claude Desktop, Cursor, and other MCP hosts — see Use Ethos as an MCP server →

License

MIT