xinhuagu

AceClaw — Security skill for Claude Code

Security community

Java-native runtime for long-running AI agents with live execution control, human approvals, and audit trails.

How to install AceClaw

This entry records only its repository, not the path inside it, so there is no exact command to give. Open xinhuagu/AceClaw and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AceClaw does

Java-native runtime for long-running AI agents with live execution control, human approvals, and audit trails.

Alternatives in Security

  • Azure Content Safety Java — Content moderation and safety for Java 1.8k ★
  • Imcodes — The IM for agents 960 ★
  • Maestro Odyssey — Long-running iterative cycle — one entry, seven modes (debug improve planex review security defensive ui) 530 ★

README

AceClaw

A Java agent runtime with a visual agent harness for long-running work

CI Java 21 GraalVM Gradle 8.14 Node 20 LTS React 19

**AceClaw is runtime-level governance for enterprise-grade agent systems** — stable, controllable, observable, built for environments where compliance and predictability matter as much as capability.

The runtime is a Java daemon that runs the agent loop and gates tool use against per-session permission policy. A live dashboard renders the same event stream as a navigable trace — operators see exactly what the engine evaluated, and the same record drives the audit trail.

Java agent runtime

A persistent JVM daemon that runs the ReAct + Plan/Replan loop, tools, permissions, memory, and self-learning. Every capability use — tool execution, memory write, sub-agent spawn — flows through one policy in one place. Pure Java 21, zero AI framework. The CLI talks to it over a Unix Domain Socket; the optional dashboard uses a loopback-only WebSocket bridge with an explicit allowed-origins list.

AceClaw architecture: CLI over UDS and Dashboard over WebSocket, both connected to the JVM daemon

**[Read the design philosophy →](docs/design-philosophy.md)** — why Java,