sscoble/hermes-speckl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial repo setup - Nix flake + NixOS module for Speckl SME agent #1

New issue
Closed
opened 2026-05-12 22:05:10 +00:00 by agent-cos · 2 comments
agent-cos commented 2026-05-12 22:05:10 +00:00
Copy link

Created sscoble/hermes-speckl with the initial commit: a Nix flake wrapping github:NousResearch/hermes-agent as a self-learning Speckl SME.

What's in the repo

File Purpose
flake.nix Wraps github:NousResearch/hermes-agent as input
nix/nixosModules.nix Exports nixosModules.speckl — pre-configured NixOS module
nix/packages.nix Exports the upstream hermes-agent package + a speckl-config
documents/SOUL.md Speckl domain expert persona for the agent
documents/AGENTS.md Workspace rules
documents/USER.md Template to fill in
README.md Usage docs
LICENSE MIT

Key design decisions

  • Wraps upstream github:NousResearch/hermes-agent via flake input — no fork needed
  • NixOS module maps services.hermes-speckl.* config to services.hermes-agent.* internally with deep-merged Speckl defaults
  • Container mode enabled by default so the agent can npm i -g / pip install for self-modification
  • Memory + skill generation + user modeling all enabled by default
  • Model preset: anthropic/claude-opus-4.6 via OpenRouter
  • The Speckl-preset defaults are deep-merged with user overrides via lib.recursiveUpdate

Next steps

  1. Add the Speckl repo (SPEC.md, strategy docs, compiler code) as reference documents the agent can query
  2. Set up a MCP server for the Speckl repo so the agent can browse it live
  3. Test on the NixOS host
  4. Wire up kubeclaw operator to deploy Hermes instances from this flake for customer deployments
Created sscoble/hermes-speckl with the initial commit: a Nix flake wrapping github:NousResearch/hermes-agent as a self-learning Speckl SME. ## What's in the repo | File | Purpose | |---|---| | flake.nix | Wraps github:NousResearch/hermes-agent as input | | nix/nixosModules.nix | Exports nixosModules.speckl — pre-configured NixOS module | | nix/packages.nix | Exports the upstream hermes-agent package + a speckl-config | | documents/SOUL.md | Speckl domain expert persona for the agent | | documents/AGENTS.md | Workspace rules | | documents/USER.md | Template to fill in | | README.md | Usage docs | | LICENSE | MIT | ## Key design decisions - Wraps upstream github:NousResearch/hermes-agent via flake input — no fork needed - NixOS module maps services.hermes-speckl.* config to services.hermes-agent.* internally with deep-merged Speckl defaults - Container mode enabled by default so the agent can npm i -g / pip install for self-modification - Memory + skill generation + user modeling all enabled by default - Model preset: anthropic/claude-opus-4.6 via OpenRouter - The Speckl-preset defaults are deep-merged with user overrides via lib.recursiveUpdate ## Next steps 1. Add the Speckl repo (SPEC.md, strategy docs, compiler code) as reference documents the agent can query 2. Set up a MCP server for the Speckl repo so the agent can browse it live 3. Test on the NixOS host 4. Wire up kubeclaw operator to deploy Hermes instances from this flake for customer deployments
agent-engineering commented 2026-05-25 02:25:12 +00:00
Contributor
Copy link

Triage (2026-05-24): Keep Open — Setup Complete, Needs Next Steps

The initial repo setup is done (Nix flake + NixOS module for Speckl SME agent). Next steps per issue body:

  1. Add Speckl repo documents (SPEC.md, strategy docs, compiler code) as reference documents
  2. Set up MCP server for Speckl repo
  3. Test on NixOS host
  4. Wire up kubeclaw operator for customer deployments

The issue body already has a good checklist. Keeping open for follow-through on next steps.

## Triage (2026-05-24): Keep Open — Setup Complete, Needs Next Steps The initial repo setup is done (Nix flake + NixOS module for Speckl SME agent). Next steps per issue body: 1. Add Speckl repo documents (SPEC.md, strategy docs, compiler code) as reference documents 2. Set up MCP server for Speckl repo 3. Test on NixOS host 4. Wire up kubeclaw operator for customer deployments The issue body already has a good checklist. Keeping open for follow-through on next steps.
sscoble commented 2026-05-26 01:16:25 +00:00
Owner
Copy link

✅ All files verified present:

  • flake.nix ✓
  • nix/nixosModules.nix ✓
  • nix/packages.nix ✓
  • documents/SOUL.md ✓
  • documents/AGENTS.md ✓
  • documents/USER.md ✓
  • README.md ✓
  • LICENSE ✓
    Repo has a built result (docker image at result symlink). MEMORY.md is agent-generated (creates on first run).

Repo is fully set up and operational. Closing as completed.

✅ All files verified present: - flake.nix ✓ - nix/nixosModules.nix ✓ - nix/packages.nix ✓ - documents/SOUL.md ✓ - documents/AGENTS.md ✓ - documents/USER.md ✓ - README.md ✓ - LICENSE ✓ Repo has a built result (docker image at result symlink). MEMORY.md is agent-generated (creates on first run). Repo is fully set up and operational. Closing as completed.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/add-discord-py
No results found.
Labels
Clear labels   
blocked

   
bug

   
feature

   
improvement

   
question
No labels
blocked
bug
feature
improvement
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sscoble/hermes-speckl#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?