You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**📜 Audit Logging**: Tamper-evident, hash-chained logs with explainable decision tooltips.
28
+
-**🖥️ Web Dashboard**: Modern, dark-mode GUI for live monitoring and management.
29
+
30
+
## 🖼️ Gallery
31
+
32
+
### Dashboard
33
+
34
+
The V4 Dashboard features a dedicated **Security Operations Center** with:
35
+
36
+
-**Active Security Envelope**: Visual confirmation of sandbox isolation.
37
+
-**OpenClaw Status**: Real-time connection health and latency metrics.
38
+
-**Explainable Audits**: Tooltips explaining _why_ an action was allowed or denied.
39
+
40
+

41
+
42
+
### Audit Timeline
43
+
44
+

45
+
46
+
### Skill Registry
47
+
48
+

26
49
27
50
## 📦 Installation
28
51
@@ -82,20 +105,21 @@ Check the immutable log of actions:
82
105
This section shows how to integrate OpenClaw agents with AegisClaw while preserving AegisClaw's security guarantees (sandboxing, scoped permissions, audit logging).
83
106
84
107
Prerequisites
108
+
85
109
- AegisClaw built and configured (see Quick Start)
86
110
- Docker installed and running
87
111
- OpenClaw agent or skill package (container image or source)
88
112
89
113
Steps
90
114
91
-
1) Store OpenClaw credentials in AegisClaw secrets
115
+
1. Store OpenClaw credentials in AegisClaw secrets
92
116
93
117
```bash
94
118
# Store the OpenClaw API key (example)
95
119
./aegisclaw secrets set OPENCLAW_API_KEY sk-openclaw-xxxxx
96
120
```
97
121
98
-
2) Enable/configure the OpenClaw adapter
122
+
2. Enable/configure the OpenClaw adapter
99
123
100
124
AegisClaw includes an OpenClaw adapter that mediates communication between agents and external services. Enable it by creating an adapter config at `~/.aegisclaw/adapters/openclaw.yaml`:
101
125
@@ -106,7 +130,7 @@ api_key_secret: "OPENCLAW_API_KEY" # name in aegisclaw secrets
106
130
timeout_ms: 5000
107
131
```
108
132
109
-
3) Register your OpenClaw-based skill/agent (manifest)
133
+
3. Register your OpenClaw-based skill/agent (manifest)
110
134
111
135
Create a skill manifest that AegisClaw can run in the sandbox. Example `skills/web-search.yaml`:
112
136
@@ -128,7 +152,7 @@ mkdir -p ~/.aegisclaw/skills
128
152
cp skills/web-search.yaml ~/.aegisclaw/skills/
129
153
```
130
154
131
-
4) Run the skill with AegisClaw's hardened runtime
155
+
4. Run the skill with AegisClaw's hardened runtime
132
156
133
157
```bash
134
158
# Run a registered skill inside the sandbox (example)
If your deployment runs an external OpenClaw service (instead of containerized skills), ensure AegisClaw's adapter will only allow the necessary egress and that API keys are provided via the secret name in the adapter config. All adapter actions are recorded in AegisClaw's audit log.
139
163
140
164
Security & Policies
165
+
141
166
- Use least-privilege scopes for skills (e.g., `files.read:/specific/path` rather than `files.read:/`).
142
167
- Require skill signing and verify signatures for production skills.
143
168
- Use the TUI approval flow for any skill that requests high-risk scopes.
144
169
145
170
Troubleshooting
171
+
146
172
- If a skill cannot reach the OpenClaw endpoint, check the egress proxy/egress rules and the adapter `endpoint` setting.
147
173
- Verify secrets are present: `./aegisclaw secrets list`
148
174
- Inspect audit logs for denied actions: `./aegisclaw logs`
@@ -179,4 +205,4 @@ Apache 2.0 - See [LICENSE](LICENSE) for details.
0 commit comments