Engineering, orchestration and securityOpen source

AGINT

Self-evolving agent framework

A native DSH bundle and preset that combines memory, reflection, scheduling, quality gates, evaluation and controlled evolution into one long-running agent system.

Project README

View on GitHub ↗
<div align="center"> ![AGINT](docs/assets/brand/png/agint-logo-512.png) </div>

English | 中文

A self-evolving agent framework built on DeepSeek Harness (dsh).

v0.27.0 · 39 mounted plugins (39 mount declarations) · 1 preset · 25 preset tool rows · 10 skills · 27 cron jobs. These are repository-level facts. Version: first row of VERSION. Plugins: node bin/verify-manifests.mjs. All other counts: the LOCAL-STATE block at the end of AGENTS.md. Live runtime numbers are not in this file.

  • Philosophy: beauty = simple + true + dependable + proactive + safe. When two of these conflict, the earlier one wins.
  • Position: dsh is the upstream runtime. AGINT is a specification plus a plugin set on top of it. It is not a fork. It is not an AGI implementation. It is the engineering skeleton for memory, reflection, constraints, metrics and evaluation. Every new feature must pass D-QAF evaluation.
  • Constitution: the D-QAF four-stage pipeline, the HARM four-dimension metrics, and the evolution memory layer. See docs/evolution-framework.md. Automation is the default. Human approval is only a fallback. Every new mechanism ships with a kill-switch, enabled out of the box, with a degraded fallback and an audit exit.

Four layers

LayerContentLocation
bundle@agint/host: all plugins plus mount patchespackage.json + cordis.patch.yml
presetThe Zhinjin (智进) persona, its tool set and its skills; 1 preset: agintpresets/agint/
plugin39 mounted plugins in 8 groups (memory / scheduling / reflection / quality / closed loop / execution / observation / perception)plugins/agint-*/
dataMemory / rules / metrics / dreams / reviewsRuntime data. It does not enter the repository.

Three sub-presets (agint-blockchain / agint-investor / agint-ops) moved to the private agint-presets repository on 2026-10-26. They ship as @agint/presets. Install this repository first.

Install

Prerequisites: Node.js ≥ 20 · python3 · dsh ≥ 0.1.7-rc.1 (matrix in VERSION) · the target profile is initialized.

git clone https://github.com/Anmulzhao/DSH-AGINT.git ~/projects/AGINT
cd ~/projects/AGINT
./install/install.sh --profile=web      # web is the default; use --profile=desktop for the desktop profile

After the install, restart the target profile. The bundle layer and the profile layer do not hot-reload. To remove AGINT, run ./install/uninstall.sh.

One preset serves every profile: $DSH_HOME/.agent-presets/agint/ holds a single file set shared by web and desktop. Its 25 tool declarations anchor to .agint-bundle/plugins/ and do not vary with --profile. The installer verifies all 25 targets and reports any that are missing.

Four hard rules:

  1. Always name the exact version when you upgrade dsh. npm i -g @deepseek-ai/dsh@latest silently downgrades.
  2. The node_modules entry inside the package is a junction to the official dsh package. rm -rf follows the link and deletes that package. Keep it when you uninstall.
  3. If the install ends with no error but nothing looks installed, the bundle is most likely not registered in dsh.profile.bundles (install step 3.5).
  4. !!js in cordis.patch.yml must be a scalar. A block collection or a template makes the whole bundle patch fail to parse. dsh then silently skips @agint/host, and the UI shows no error. Run node bin/check-patch-yaml.mjs after you edit the file.

For more troubleshooting, see docs/dsh-integration.md. For container deployment, use docker/.

Repository self-checks

After you change a plugin, run four steps in order:

  1. node bin/check-patch-yaml.mjs — the patch YAML parses.
  2. node bin/check-wiring.mjs — the wiring is live.
  3. node bin/check-dsh-compat.mjs — dsh compatibility.
  4. node bin/check-boundary.mjs — the capability boundary is clean.

The other self-checks (manifest / tool schema / memory layer / LOCAL-STATE write-back) carry their own usage notes in the scripts under bin/.

Documentation map

What you wantWhere to go
Runtime state (real numbers, authoritative)The LOCAL-STATE block at the end of AGENTS.md
Architecture / plugin detaildocs/architecture.md · docs/plugins/
dsh integration / install troubleshootingdocs/dsh-integration.md
Security boundary / kill-switch listdocs/security-boundary.md
Capability ownership / boundary rulesdocs/capability-boundary.md
Known gaps (read this before you draw a conclusion)docs/known-limitations/
Ops SOP / pitfall records / evaluation scenariosdocs/operations/ · docs/lessons/ · eval/scenarios/
Roadmap / changelog / PHILOSOPHYGitHub Wiki

Docs under docs/ are written in Chinese. This README is the only English entry point.

Three environment variables: DSH_HOME (the data root, default $HOME/.dsh) · AGINT_PROFILE (the install.sh target profile, web if unset) · AGINT_HOME, which has two meanings — install.sh reads it as the source root, while plugins read it as the data root. Set it wrong and the system writes data into the repository directory. The design note is in docker/entrypoint.sh.

License

MIT