# aiwg [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/jmagly/aiwg  
**GitHub Stars:** 229  
**npm Downloads (last month):** 45641  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aiwg

## Description
Reusable project context and specialist workflows for the AI tools you already use. AIWG places agents, skills, commands, and rules in provider-readable locations, with optional utilities for artifact memory, workflow orchestration, recovery, and discover

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/jmagly/aiwg), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

```sh
npm i -g aiwg
```

## Documentation

## What aiwg does

AIWG provides a shared source for project context and specialist workflows used by AI assistants. It packages agents, skills, commands, rules, templates, and domain frameworks for activities such as software planning, specialist reviews, campaign preparation, incident investigation, research, media curation, and operational knowledge maintenance.

The deployment layer adapts those resources to the provider selected by the project. The repository describes 19 named provider integrations, along with a generic adapter for custom or unrecognized harnesses. Provider-facing files are emitted in the locations those tools read, allowing a project to maintain one set of reusable instructions rather than separate copies.

Optional components add persistent artifact memory under `.aiwg/`, workflow orchestration, autonomous task loops, artifact indexing, cost telemetry, health diagnostics, and recovery support. Addons can extend the base framework with writing profiles, testing tools, decision support, and other task-specific capabilities.

## How it works

AIWG is installed as a Node.js command-line package and configured from the project directory. The setup flow can inspect an existing installation, identify duplicate or damaged components, and guide repair or updates. Setup first records an interview plan; review displays that plan without changing provider configuration, while apply requests confirmation and reports which actions completed.

A repeated apply operation resumes unfinished work and preserves actions that have already succeeded. Provider deployment is handled through the existing deployment owners, and the resulting report separates core readiness from optional integration failures. Direct complete-system deployment is also available through `aiwg use all --provider <provider>`.

For isolated execution, AIWG can be paired with AIWG Cockpit and a self-hosted Agentic Sandbox executor. That optional path audits the host, installs approved Docker or KVM/libvirt prerequisites, applies isolation, network, storage, and access choices, and checks the control and audit path.

## Setup and configuration

Install the main package globally with:

```bash
npm i -g aiwg
cd /path/to/your/project
aiwg setup --scope project --providers <provider>
aiwg setup --review
aiwg setup --apply
```

Provider values can include `claude`, `codex`, `copilot`, `cursor`, `omp`, and `pi`. The lightweight executable package is available as `@aiwg/cli` and resolves signed, versioned resources from the release host. Optional native features are installed separately when interactive terminals, semantic search, or graph-backed artifacts are needed.

Node.js 24 or newer is required. `aiwg doctor` checks the installation, deployed providers, missing dependencies, and selected capability probes. On systems where the global npm binary directory is not on `PATH`, `npx aiwg doctor` provides an alternative invocation.

## Tools and capabilities

- Provider-specific deployment of reusable Markdown and YAML resources
- Project setup interviews, read-only review, confirmed apply, and recovery
- Agents, skills, commands, rules, templates, and domain frameworks
- Persistent project artifacts and artifact indexing
- Workflow orchestration, autonomous loops, and background execution
- Health checks, cost telemetry, and optional decision-support utilities

## Limitations and notes

The base global installation intentionally excludes native packages whose lifecycle scripts require explicit trust. Native capabilities must be enabled individually, and AIWG stores their private manifest and lockfile in the user data directory. Optional decision offload and direct workers require explicit opt-in. The generic adapter supports custom harnesses but is separate from the named provider integrations.

_Full upstream README: https://allmcps.com/mcp/aiwg/readme_