@eep-dev/agent-adopt
v0.1.0
Published
One-shot EEP adoption for app repos: inject, apply, verify, optional framework patch, report.
Readme
@eep-dev/agent-adopt
One-shot CLI for adopting EEP in an existing application repository: runs eep-setup inject → apply → verify, optional Express / FastAPI best-effort wiring, and writes EEP_ADOPTION_REPORT.md.
Install
Published (when available): npm install -g @eep-dev/agent-adopt or use npx @eep-dev/agent-adopt.
From this monorepo, build @eep-dev/setup-cli first (types and runtime come from dist/, not committed to git), then this package:
cd packages/@eep-dev/setup-cli && npm install && npm run build
cd ../agent-adopt && npm install && npm run build
node dist/index.js --project /path/to/app --no-complianceUsage
npx @eep-dev/agent-adopt --project . --no-compliance| Flag | Meaning |
|------|--------|
| --project, -p | App root (default: cwd) |
| --config | eep-setup.json path |
| --output | eep-generated directory |
| --answers | Non-interactive answers for inject |
| --no-patch | Skip Express/FastAPI file patchers |
| --no-compliance | Do not run live compliance-cli |
| --compliance-target | Base URL for npx @eep-dev/compliance-cli |
| --compliance-api-key, --compliance-entity | Passed through to compliance CLI |
| --report | Report path (default: ./EEP_ADOPTION_REPORT.md) |
Requirements
- Node 18+ for this package;
@eep-dev/compliance-clirecommends Node 22+ when you use live checks. - Runtime wiring still needs
@eep-dev/middleware/eep-middleware-pythonin the target app (see EEPdocs/guides/integrate-eep-after-setup-cli.md).
See also
License: Apache-2.0
