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
_Added: 2026-03-09 | Source: Framework research (Anthropic Skills guide, OpenAI Agents SDK, Google ADK)_
3
4
4
5
These features are NOT part of the initial roadmap. Build them AFTER the v4 mockup is 100% complete and verified.
@@ -8,44 +9,51 @@ These features are NOT part of the initial roadmap. Build them AFTER the v4 mock
8
9
## 🔴 High Priority (unlocks "App Factory" overnight runs)
9
10
10
11
### 1. Iterative Refinement Loop
12
+
11
13
**What:** Verification doesn't stop at one tsc pass. Loop: run tsc → errors? → send back to agent → fix → re-run. Max 3 iterations before escalating to human review.
12
14
**Why:** Anthropic explicitly identifies this as the pattern that makes agents reliable. Current single-pass fails silently.
### 2. Agent Handoffs (Context Passing Between Agents)
19
+
17
20
**What:** When one agent finishes a wave, it passes structured context (git diff, error log, what it built, what it skipped) to the next agent. No more blind starts.
18
21
**Why:** Current agents start each task cold. Handoffs are first-class in OpenAI Agents SDK — explicit control transfer with context. This is what keeps overnight runs coherent.
19
22
**Where:** New `workspace-daemon/src/handoff.ts`, update adapter interfaces
**What:** Agent routing logic that picks different tools based on file size, task type, and context. Large refactors → Codex. Small surgical fixes → Claude ACP session. Research tasks → Claude with web search.
@@ -54,30 +62,33 @@ These features are NOT part of the initial roadmap. Build them AFTER the v4 mock
54
62
## 🔵 Lower Priority (Enterprise / Scale)
55
63
56
64
### 7. Session Persistence Surfaced to Agents
65
+
57
66
**What:** Pass previous run context (what worked, what failed, git history) to agent at start of each task. Agents currently start blind even when re-running.
58
67
**Where:** Update adapter `buildPrompt()` to include run history from SQLite
59
68
60
69
### 8. Progressive Skill Loading for Agent Prompts
70
+
61
71
**What:** Agent system prompts use Anthropic's 3-level progressive disclosure — minimal header always loaded, full instructions only when triggered, reference docs on demand.
62
72
**Why:** Keeps context lean when running many agents in parallel.
**What:** Define agent "skills" as portable SKILL.md-style files that can be shared, versioned, and swapped. A "React Builder" skill vs "Python API Builder" skill.
67
78
**Pattern source:** Anthropic agentskills.io open standard
68
79
69
80
---
70
81
71
82
## Summary Table
72
83
73
-
| Feature | Impact | Effort | Priority |
74
-
|---------|--------|--------|----------|
75
-
| Iterative refinement loop | 🔥 High | Low | Do first |
76
-
| Agent handoffs | 🔥 High | Med | Do second |
77
-
| Specialized agent roles | 🔥 High | High | Do third |
78
-
| Parallel guardrails | Med | Med | After roles |
79
-
| Rollback on rejection | Med | Low | After roles |
80
-
| Context-aware tool selection | Med | High | Later |
Copy file name to clipboardExpand all lines: SECURITY.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ If you discover a security vulnerability in Hermes Workspace, please report it r
6
6
7
7
**Do NOT open a public GitHub issue for security vulnerabilities.**
8
8
9
-
Instead, email: **security@hermesworkspace.app**
9
+
Instead, report via [GitHub Security Advisories](https://github.com/outsourc-e/hermes-workspace/security/advisories) or DM [@ericousodev on X](https://x.com/ericousodev).
10
10
11
11
We will acknowledge your report within 48 hours and aim to provide a fix within 7 days for critical issues.
12
12
@@ -28,28 +28,33 @@ We will acknowledge your report within 48 hours and aim to provide a fix within
28
28
## Security Measures (v3.0.0+)
29
29
30
30
**Authentication**
31
+
31
32
- All API routes require authentication as of v3.0.0
32
33
- Session tokens use timing-safe comparison to prevent timing attacks
33
34
- httpOnly + SameSite=Strict cookies
34
35
- Token revocation on logout
35
36
36
37
**Network**
38
+
37
39
-`Access-Control-Allow-Origin` restricted to localhost — no wildcard CORS
38
40
- Browser proxy and screenshot endpoints locked to same-origin only
39
41
- Rate limiting on high-risk endpoints (file access, debug, exec)
40
42
41
43
**Data & File Access**
44
+
42
45
- Path traversal prevention on all file and memory routes (`ensureWorkspacePath()`)
43
46
-`.md`-only restriction on memory write routes
44
47
- No API keys or secrets ever exposed to client-side code
45
48
- Hermes tokens are server-side only
46
49
- Diagnostic output scrubbed of sensitive data
47
50
48
51
**Agent Safety**
52
+
49
53
- Exec approval workflow — sensitive Hermes exec commands require explicit human approval via in-UI modal
50
54
- Skills security scanning — every skill from the marketplace is scanned for suspicious patterns before install
51
55
52
56
**Configuration**
57
+
53
58
- Environment files are gitignored
54
59
- Config endpoints redact credentials in responses
55
60
- Example configs use placeholder keys only
@@ -69,9 +74,8 @@ We will acknowledge your report within 48 hours and aim to provide a fix within
Copy file name to clipboardExpand all lines: docs/hermes-openai-compat-spec.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ We want to reverse that.
37
37
This is the decision to lock in:
38
38
39
39
> **Hermes Workspace must work standalone against any OpenAI-compatible backend.**
40
-
>
40
+
>
41
41
> Hermes-specific workspace features may enhance the experience when the full Hermes API is available, but the product must remain usable without those endpoints.
42
42
43
43
Non-negotiable implication:
@@ -365,9 +365,9 @@ This is not the detailed task plan, but the engineering direction should be:
365
365
Lock this in:
366
366
367
367
> Hermes Workspace is a standalone frontend for OpenAI-compatible chat backends.
368
-
>
368
+
>
369
369
> Hermes-native APIs are an enhancement layer, not a requirement.
370
-
>
370
+
>
371
371
> Step 1 is portable compatibility now.
372
-
>
372
+
>
373
373
> Step 2 is upstreaming the enhanced Hermes APIs so no fork is needed ever again.
0 commit comments