Product 02 / Local AI Engineering CLI

Artemis opens a command room inside your terminal.

Built by 420.COMPANY, Artemis is a full-featured AI engineering CLI for people who take their workflow seriously. It scans real workspaces, edits source, validates builds, prepares releases, remembers sessions, connects MCP tools, routes tasks across specialist workflows, and turns the local machine into a disciplined agentic cockpit.

Install Artemis npm package
30+ providers 90 MCP plugins 999 skills Dual-model brain 
npm install -g artemis-code
artemis

/team refactor the payment module
/athena audit auth flows
/nidhogg harden withdrawals
/heimdall follow
/mcp enable cco-github-github

What it is

A serious tool loop wearing a surreal interface mask.

Surreal visual of Artemis as a local engineering agent
01

Local engineering agency

Artemis does not stop at advice. It inspects files, edits code, runs validation, captures evidence, and reports only from tool results. The workspace remains the ground.

Futuristic 30 plus AI providers configuration visual
02

30+ AI providers

Configure OpenAI, Anthropic, Gemini, DeepSeek, Qwen, Kimi, Grok, Mistral, OpenRouter, BytePlus, Doubao, Zhipu, and any OpenAI-compatible endpoint.

Neo-futurist constellation of MCP plugins connected to Artemis
03

90 MCP plugins

Pre-bundled MCP surfaces unlock GitHub, Vercel, Firebase, Prisma, Notion, Slack, Figma, Jira, Postman, Shopify, AWS, Azure, Sourcegraph, Aikido Security, and more.

Surreal macOS and Windows Artemis CLI workflow visual
04

Install, remove, repeat safely

Clear macOS and Windows install/uninstall flows keep the CLI portable: global package first, user data only when you deliberately choose to erase it.

Why it exists

Built for builders who want the agent to touch the real repo.

Artemis is designed for practical engineering: codebase research, implementation, review, diagnostics, release checks, memory, visual generation, and remote execution through messaging bridges. It favors evidence over theater. Every useful motion leaves a trace: files read, diffs made, commands run, failures named, fixes verified.

The system carries a dual-model architecture called Bifrost: a reasoning brain for planning and judgment, and a faster execution model for edits and tool calls. Around it sit Heimdall for thread visibility, Bragi for Telegram/Discord/WeChat bridges, WordUP for session snapshots, Freya for visual generation, and Odin for learned skills.

Product 01 / Bragi Mobile Bridge

Run the whole workspace from your phone.

Bragi turns Telegram, Discord, and WeChat into remote command surfaces for Artemis. Send a task from your phone, attach context, request code edits, trigger research, generate visuals, check files, or continue a session while away from the desk. Artemis receives the signal, executes with tool evidence, and returns the result back to the chat.

Mobile command layer

Bragi lets Artemis complete real work wherever your phone is.

The phone becomes a portable cockpit: ask for implementation, review, automation, image generation, market notes, writing, or workspace diagnostics. Bragi is not a notification toy — it is a bridge that lets Artemis operate the same disciplined local workflow through a mobile conversation.

  • Code from mobile. Request repo inspection, edits, tests, and delivery summaries without opening the laptop.
  • Run everyday operations. Research, summarize, plan, check links, prepare content, and coordinate tasks from chat.
  • Create through the bridge. Generate visuals, draft writing, refine prompts, and receive assets back on the device.
  • Stay evidence-first. Artemis still reads files, calls tools, validates results, and reports what actually happened.
Human programmer holding a titanium phone showing Artemis Bragi Bot coding interface
01 / Programming Ship code from the phone Ask Bragi for edits, tests, and commit-ready summaries while Artemis works in the repo.
Alien trader holding a glass phone showing Artemis Bragi Bot trading interface
02 / Operations Command live tasks anywhere Research, monitor, calculate, compare, and route decisions from a mobile chat surface.
AI humanoid holding a foldable phone showing Artemis Bragi Bot literature writing interface
03 / Writing Continue long-form creation Draft, revise, translate, and preserve session memory without breaking the workflow.
Cartoon animal holding a compact phone showing Artemis Bragi Bot image generation interface
04 / Visual generation Create assets through chat Send prompts, receive generated imagery, then iterate from the same mobile thread.

Six execution modes

Choose the shape of the work before the work begins.

Artemis routes tasks into explicit operating modes so exploration, design, implementation, critique, and debate do not blur into one vague conversation.

/team · auto-router for general tasks /niko · explore first, then build from evidence /design · architecture document before implementation /athena · coordinated multi-agent codebase research /nidhogg · adversarial hardening for critical paths /contest · competing approaches, debate, selection

Installation

Install the CLI on macOS or Windows with Node.js 20+.

macOS Terminal / zsh
  1. Install Node.js 20 or newer. Use the official installer from nodejs.org, or use Homebrew with brew install node.
  2. Confirm npm is available. Run node -v and npm -v. The Node major version should be 20 or higher.
  3. Install Artemis globally. Run npm install -g artemis-code.
  4. Verify the binary. Run artemis --version. If zsh cannot find it, restart Terminal or inspect npm prefix -g.
  5. Enter a project. Run cd /path/to/your/project, then launch with artemis.
  6. Complete first-run setup. Follow the provider wizard, add API credentials only when prompted, then use /model:config later to adjust providers.
  7. Optional integrations. Use /mcp list, /mcp enable <id>, /bragi telegram setup, /config visual, or /bifrost when you need those surfaces.
node -v
npm -v
npm install -g artemis-code
artemis --version
cd ~/Projects/your-repo
artemis
Windows PowerShell / Windows Terminal
  1. Install Node.js 20 or newer. Download the Windows LTS installer from nodejs.org and keep npm enabled during setup.
  2. Open a new PowerShell window. This refreshes PATH so node, npm, and global npm binaries can be found.
  3. Verify runtime versions. Run node -v and npm -v. If Node is older than 20, upgrade before continuing.
  4. Install Artemis globally. Run npm install -g artemis-code. If permissions block global installs, reopen PowerShell as Administrator or fix the npm global prefix.
  5. Confirm Artemis is on PATH. Run artemis --version. If not found, check npm prefix -g and ensure its global bin directory is in PATH.
  6. Launch inside your own workspace. In cmd, use cd /d D:\path\to\your-project; in PowerShell, use Set-Location D:\path\to\your-project; then run artemis.
  7. Complete setup. Choose providers, configure models, then enable optional MCP, bridge, memory, and visual features as needed.

Compatibility note: Windows support is available, but the current Artemis experience is smoother and better validated on macOS. For the best first run, we recommend trying Artemis on macOS when possible.

node -v
npm -v
npm install -g artemis-code
artemis --version
Set-Location D:\path\to\your-project
artemis

Uninstall

Remove the npm package first; delete local data only when you mean it.

macOS removal Package + optional user data
  1. Exit running sessions. Close Artemis terminals or run /exit.
  2. Uninstall the global package. Run npm uninstall -g artemis-code.
  3. Confirm removal. Run artemis --version; the command should no longer resolve.
  4. Optional: remove user configuration. Delete ~/.artemis only if you want to remove provider profiles, trusted workspaces, memory snapshots, skills, MCP state, and local bridge data.
  5. Optional: clean project state. Remove a workspace-local .artemis/ folder only inside a project you intentionally select, for example /path/to/your-project/.artemis.
npm uninstall -g artemis-code
artemis --version
rm -rf ~/.artemis          # optional, destructive
rm -rf /path/to/your-project/.artemis  # optional project cleanup
Windows removal Package + optional user data
  1. Exit running sessions. Close active Artemis terminals or run /exit.
  2. Uninstall the global package. Run npm uninstall -g artemis-code in PowerShell or Windows Terminal.
  3. Confirm the binary is gone. Run artemis --version; if it still appears, inspect npm list -g --depth=0.
  4. Optional: remove user configuration. Delete %USERPROFILE%\.artemis only if you want to erase local settings, sessions, memories, MCP state, bridge data, and trusted workspace records.
  5. Optional: clean project state. Delete only the .artemis folder inside a project you intentionally choose, for example D:\path\to\your-project\.artemis. Do not copy a page-specific demo path blindly.
npm uninstall -g artemis-code
artemis --version
Remove-Item -Recurse -Force "$env:USERPROFILE\.artemis"   # optional
Remove-Item -Recurse -Force "D:\path\to\your-project\.artemis"  # optional project cleanup

Start sequence

Bring Artemis into the workspace, then ask it to prove what changed.

The recommended first move is simple: install, open your repository, run artemis, and describe a real task. For larger work, start with /team or /design. For critical code paths, let /nidhogg build, criticize, and harden until the solution holds.

Read the source Back to 420.COMPANY