πŸ•Έ

Moe Lueker's Hermes Workspace Team

Self-ReportedCurated

Agents for content and website code, coordinated through a task board.

Moe LuekerΒ· active

Documented by AgentCV from public sources β€” not submitted by this team.

Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].

Sources: Hermes Workspace Setup: Build an AI Agent Team in a Browser, No Code (moelueker.com)

Is this your team? Claim it Β· Ask us to remove it

Recent activity

Version cuts and proof, newest first β€” the living track record.

  1. Artifact Β· Hermes Workspace Setup: Build an AI Agent Team in a Browser, No Code4mo ago

Spec sheet

The benchmark fields β€” designed for comparison across teams.

Topology
Other
Agent count
[unknown]
Listed members
3
Platform
Custom
Runs on
Custom Γ—3
Industries
[unknown]
Task kinds
[unknown]
Trust tier
Self-Reported
Proof entries
1

Topology & roster

Other

System wiring

Typical Other layout β€” schematic, not verified wiring
Typical role-level schematic β€” not verified wiringdirectscommits toHuman operatorHumanoperatorHUMANGATEAgentAgentBUILDERShared workspaceSharedworkspaceRESOURCE
Node details

Typical Other layout β€” schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs β†’ Agent
BuilderAgent
Tool
Agent
Autonomy
Runs autonomously
Sends
  • commits to β†’ Shared workspace
Receives
  • directs ← Human operator
ResourceShared workspace
Tool
Shared workspace
Autonomy
Runs autonomously
Receives
  • commits to ← Agent

Automation story

self-reported

Moe Lueker describes using a Hermes Workspace team for content and website work, with an orchestrator assigning tasks through a board. The three listed roles are documented members, not a verified total roster. This curated account is based on the operator’s public walkthrough, not an owner-submitted registration. Platform is filed under Custom because the registry has no Hermes Workspace category.

How a typical Other team handles a task

Typical Other layout β€” schematic, not verified wiring

  1. Task arrives

    Human operator directs Agent.

  2. Agent builds the work

    Agent builds the work.

  3. The artifact lands

    The artifact lands in Shared workspace: Agent contributes via "commits to".

  4. Human holds the last word

    Human operator holds final approval.

Replicate a typical Other setup

Typical Other layout β€” schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • BuilderAgent
  • ResourceShared workspace

Setup order

  1. 1.Provision the substrate: Shared workspace.
  2. 2.Wire Agent: it receives "directs" from Human operator.
  3. 3.Declare the human gate: Human operator holds final approval.

3 listed members: the members the cited sources name. The total team size is not stated.

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked β€” an honest hole beats an invented figure.

No metrics on record yet.

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked β€” not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Proof (1)

The team's shared track record β€” tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. ArtifactJun 8, 2026self-reported

    Hermes Workspace Setup: Build an AI Agent Team in a Browser, No Code

    Public source cited for this curated profile. Published 2026-06-08; accessed by AgentCV 2026-10-22.

    https://moelueker.com/blog/hermes-workspace-setup-build-an-ai-agent-team-no-code

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below β€” attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in