Back to directory

helloagents

Maintenance: Active

hellowind777/helloagents

Autonomous AI companion that doesn't just analyze problems — it keeps working until the implementation is built and verified.

View on GitHub
$ npm install -g --allow-scripts=helloagents helloagents

705

stars

99

forks

JavaScript

Language

NOASSERTION

License

2025-09-26

Created

2026-09-06

Last push

Apache-2.0 workflow layer (skills, project knowledge, delivery checks, resumable state) for Claude Code, Gemini CLI, Grok, Cursor and Codex CLI; the README does not document any DeepSeek Harness (dsh) integration.

DSH integration

Ecosystem-related

Author-claimed

Safety audit

Unaudited

Last verified

2026-08-21

License

Apache-2.0

01What can it help you accomplish?

  • Make an AI coding CLI plan, implement, and verify work to delivery instead of stopping at advice

    Structured workflow stages with plan packages (requirements.md, plan.md, tasks.md, contract.json), 14 stage-specific quality skills, and delivery evidence recorded in session artifacts

    Developers using Claude Code, Gemini CLI, Grok Build, Cursor, or Codex CLI who want the agent to keep working until a task is built, tested, and verified

  • Keep persistent project knowledge and resumable execution state across CLI sessions

    A `.helloagents/` knowledge base (context.md, guidelines.md, verify.yaml, modules/, plans/) plus per-workspace session STATE.md snapshots that make long tasks resumable

    Teams running long multi-session coding tasks who do not want to re-explain the repo or lose plan context between sessions

02How to install into DeepSeek Harness

Prerequisites

  • Node.js >= 18 (per the README's node badge)
  • npm — on npm 11 and later, keep `--allow-scripts=helloagents` on direct install or upgrade commands
  • One of the supported host AI coding CLIs: Claude Code, Gemini CLI, Grok Build, Cursor, or Codex CLI

Installation steps

  1. 01

    Install the package globally: `npm install -g --allow-scripts=helloagents helloagents` (use the `helloagents-js` alias if another `helloagents` executable already exists in PATH)

    $ npm install -g --allow-scripts=helloagents helloagents

  2. 02

    Deploy to a host CLI: `helloagents install codex --standby` for selected projects, or `helloagents install --all --global` for full rules everywhere

  3. 03

    Restart the target AI CLI or open a new session — already running sessions do not reload injected rules automatically

  4. 04

    Inside the AI CLI chat, run `~init` to initialize the project workflow and sync the project knowledge base

Verify the integration

  • Type `~help` in the AI CLI chat — you should see the available chat commands and the current settings

Rollback

  • Run `helloagents cleanup <target>` to remove managed injections and links (e.g. `helloagents cleanup claude --global`)
  • Run `npm explore -g helloagents -- npm run uninstall -- --all` before `npm uninstall -g helloagents` so host integrations are cleaned; project `.helloagents/` files and `~/.helloagents/helloagents.json` are intentionally preserved

03DSH integration and capability boundaries

DSH integrationEcosystem-related

Workflow layer for AI coding CLIs (Claude Code, Gemini CLI, Grok Build, Cursor, Codex CLI); the README documents no DeepSeek Harness / dsh integration, so this is an ecosystem tool rather than a DSH plugin

  • 14 stage-specific workflow skills

    coding tasks of any stage (UI, API, security, tests, data, architecture, debugging, docs…)task-appropriate quality rules loaded on demand — simple tasks stay light, complex work gets stricter checks

  • Chat commands for every work style

    `~ask`, `~auto`, `~plan`, `~build`, `~prd`, `~loop`, `~init`, `~test`, `~qa`, `~commit`, `~clean`, `~help` typed in the host CLI chatrouted workflow stages — clarification, planning, implementation, QA loop, commit and closeout

    most commands write plan, knowledge, and state files under `.helloagents/`; only `~ask` is pure conversation with no files created
  • Safer host-CLI lifecycle management

    `helloagents install / update / cleanup / uninstall / doctor / switch-branch` shell commandsmanaged config writes to the selected host CLI, drift diagnostics, and scoped cleanup

    writes and updates host config files — e.g. `~/.claude/CLAUDE.md`, `~/.claude/settings.json`, `~/.codex/AGENTS.md`, `~/.codex/config.toml`, `~/.codex/hooks.json` — plus symlinks back to the `~/.helloagents/helloagents` runtime rootthe one-shot install scripts download and execute a remote shell/PowerShell script from raw.githubusercontent.com
  • Verification and delivery evidence

    the `~qa` quality loop and delivery gates at closeoutstructured receipts in session `artifacts/` (qa-review.json, advisor.json, visual.json, closeout.json) proving review, verification commands, and closeout

    writes session state and evidence files under `.helloagents/sessions/`; standard runtime evidence expires after 72 hourswhen `auto_commit_enabled` is true, closeout auto-creates a local commit if verification passed and the working tree changed

04Who is it for? When not to use it?

Good for

  • Developers using Claude Code, Gemini CLI, Grok Build, Cursor, or Codex CLI who want the agent to keep working until a task is built, tested, and verified
  • Teams running long multi-session coding tasks who do not want to re-explain the repo or lose plan context between sessions

Not for

  • The README documents integrations only for Claude Code, Gemini CLI, Grok Build, Cursor, and Codex CLI — DeepSeek Harness (dsh) is not among the supported host CLIs.
  • Standby mode writes into the host CLI's own config files (e.g. `~/.claude/CLAUDE.md`, `~/.claude/settings.json`, `~/.codex/config.toml`, `~/.codex/hooks.json`), so installing or cleaning up affects the host CLI globally; `helloagents doctor` exists to detect drift.

05Compatibility, maintenance and safety notes

  • The README documents integrations only for Claude Code, Gemini CLI, Grok Build, Cursor, and Codex CLI — DeepSeek Harness (dsh) is not among the supported host CLIs.
  • Standby mode writes into the host CLI's own config files (e.g. `~/.claude/CLAUDE.md`, `~/.claude/settings.json`, `~/.codex/config.toml`, `~/.codex/hooks.json`), so installing or cleaning up affects the host CLI globally; `helloagents doctor` exists to detect drift.
  • Requires Node.js >= 18 and npm; on npm 11+ direct installs and upgrades must keep the `--allow-scripts=helloagents` flag so the managed postinstall can run. Inferred: the latest published release is a beta tag (v4.0.5-beta.1) while the README documents v3.1.9, so release lines may drift.
2025-09-262026-08-14v4.0.5-beta.1

Apache-2.0 · actively maintained (last push 2026-08-14, latest release v4.0.5-beta.1)

06Frequently asked questions

Does HelloAGENTS integrate with DeepSeek Harness (dsh)?

The README does not document any DeepSeek Harness integration. The supported host CLIs are Claude Code, Gemini CLI, Grok Build, Cursor, and Codex CLI, deployed in standby or global mode through the `helloagents install` commands.

How do I install HelloAGENTS?

Run `npm install -g --allow-scripts=helloagents helloagents` (Node >= 18; keep the --allow-scripts flag on npm 11+), then deploy to a host CLI with `helloagents install codex --standby` for selected projects or `helloagents install --all --global` for host-wide full rules. Restart the target CLI afterwards.

How do I verify it is working?

Type `~help` in your AI CLI chat — you should see the available chat commands and the current settings. Then run `~init` inside a repo to initialize the project workflow and sync the knowledge base. `helloagents doctor` reports drift in managed host files.

What files does it write?

Project knowledge, plans, and session state live under `.helloagents/` in the project, with user-level config at `~/.helloagents/helloagents.json`. Standby mode also writes managed blocks into the host CLI's own config (e.g. `~/.claude/CLAUDE.md`, `~/.codex/config.toml`), and cleanup/uninstall removes exactly those managed entries.

What is the difference between standby and global mode?

Standby is lighter and explicit: it deploys rules to selected CLIs and leaves each repo uninitialized until you run `~init`. Global applies full rules at the host level, using native plugin/extension/marketplace installs on Claude, Gemini, Grok, Cursor, and Codex.

08Data and sources

  • Author-claimedgithub.com79c0b482fd20…

    HelloAGENTS adds a workflow layer on top of Claude Code, Gemini CLI, Grok Build, Cursor, and Codex CLI.

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-21. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.