Commit Graph
439 Commits
Author SHA1 Message Date
m3ta-chiron 8b7d52f5d4 Merge pull request 'refactor(m3-hermes): use the T3 Code module from m3ta-home' (#33) from feat/m3-hermes-t3code-module into master 2026-11-03 18:10:31 +01:00
m3ta-chiron 26bc5b5562 Merge pull request 'chore(flake): update inputs and drop unsupported systems' (#34) from chore/flake-update into master 2026-11-03 18:10:30 +01:00
m3ta-chironandClaude Opus 5.5 464de584a4 chore(flake): update inputs and drop unsupported systems
Full flake update. Drops x86_64-darwin (unsupported by nixpkgs 26.11) and
i686-linux (agenix and colmena publish no packages for it), so
`nix flake check --all-systems` passes. m3ta-nixpkgs and m3ta-home carry
the fixes the new nixpkgs and home-manager need.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 18:10:06 +01:00
m3ta-chironandClaude Opus 5.5 6a608a8e6a refactor(m3-hermes): use the T3 Code module from m3ta-home
The server now binds the NetBird address of wt0 instead of 0.0.0.0, so
the pairing URL is reachable from mesh peers, and the port opens on wt0
via the module instead of hand-written ip46tables rules. The agent
runtime (agent-lib sync, Claude skills, Gitea SSH) stays host-specific.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 18:03:04 +01:00
m3ta-chiron effbdd04dc Merge pull request 'chore(flake): bump m3ta-nixpkgs and m3ta-home' (#32) from fix/bump-m3ta-inputs into master 2026-11-03 17:38:54 +01:00
m3ta-chironandClaude Opus 5.5 cc5f85c1cc chore(flake): bump m3ta-nixpkgs and m3ta-home
Picks up the vibetyper fix that drops fuse2, which newer nixpkgs removed;
the next nixpkgs bump would otherwise fail on every desktop host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 16:20:34 +01:00
Sascha KönigandClaude Opus 5.5 93e4429ab0 Merge branch 'feat/t3code-module': T3 Code from the m3ta-home module
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 12:27:54 +01:00
Sascha KönigandClaude Opus 5.5 09f509c37b refactor(secrets): rename agent Gitea tokens per instance, add work token for m3-kratos
hermes-gitea-token.age is renamed unchanged to agent-gitea-token-m3ta.age. agent-gitea-token-az.age carries the m3ta-chiron token for git.az-gruppe.com, for m3-kratos only. Also bumps m3ta-home to the T3 Code module.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 12:27:54 +01:00
Sascha KönigandClaude Opus 5.5 aef9d84d61 refactor(m3-kratos): use the T3 Code module from m3ta-home
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 08:02:07 +01:00
m3ta-chiron ba302a8a00 Merge pull request 'feat(m3-kratos): run T3 Code as a service on the NetBird IP' (#31) from feat/m3-kratos-t3code-service into master
Reviewed-on: #31
2026-11-01 13:54:18 +01:00
m3ta-chironandClaude Opus 5.5 845af0e897 feat(m3-kratos): run T3 Code as a service on the NetBird IP
The desktop app ignores --host, so its LAN host override goes away too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:49:19 +01:00
m3ta-chiron 8f52714343 Merge pull request 'fix(m3-kratos): advertise T3 Code on the NetBird name' (#30) from fix/m3-kratos-t3code-lan-host into master
Reviewed-on: #30
2026-11-01 13:38:40 +01:00
m3ta-chironandClaude Opus 5.5 773ec3e4f9 fix(m3-kratos): advertise T3 Code on the NetBird name
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:35:13 +01:00
m3tam3re d4cc6d80d8 Merge branch 'fix/m3-kratos-t3code-firewall' 2026-11-01 13:27:48 +01:00
m3tam3re 0c52f97bde Merge branch 'fix/t3code-gitea-provider' 2026-11-01 13:27:48 +01:00
m3tam3re 1cf5cb44ea Merge branch 'chore/remove-fish' 2026-11-01 13:27:48 +01:00
m3tam3reandClaude Opus 5.5 ee0a8908d0 feat(m3-kratos): allow T3 Code port from the NetBird mesh
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:26:53 +01:00
m3tam3reandClaude Opus 5.5 5a66da916d fix(t3code): recognize code.m3ta.dev as Gitea for change requests
T3 only detects a Gitea on a custom domain through a matching tea or fj
login, so creating a change request failed with "No unknown source control
provider is registered". Put tea on T3's PATH with an m3ta-chiron login built
at runtime from the hermes-gitea-token agenix secret.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:24:11 +01:00
m3ta-chironandClaude Opus 5.5 b20861c991 chore: stop tracking the Beads gate lock
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:23:40 +01:00
m3tam3re 8a9fb31c9a chore: remove fish shell from host configs
- Drop fish.enable from the desktop, portable, and server shell profiles in hosts/common/users/m3tam3re.nix
- Remove programs.fish.enable from m3-atlas, m3-helios, m3-hermes, and m3-kratos
2026-11-01 13:19:03 +01:00
m3ta-chironandClaude Opus 5.5 d25015bc9d fix(t3code): run T3 agents as m3ta-chiron on every host
The identity lived in the m3-hermes service and in home-manager session
variables. Neither reaches the T3 desktop app on m3-kratos, so its agents
committed and pushed as m3tam3re. Wrap the T3 packages via an overlay so
everything T3 spawns inherits commit identity and Gitea push auth,
independent of host and launcher.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:14:02 +01:00
m3tam3reandClaude Opus 5.5 a2d226583f fix(t3code): provide Beads to T3 Code agents on m3-hermes
bd was neither on the t3code service PATH nor on the system. Add it to
both, like the harnesses, and set BEADS_ACTOR so the audit trail matches
the m3ta-chiron commit identity.

Also take the bd 1.3.2 migration of .beads (config, gitignore, hooks) and
ignore the .beads.gate.lock it creates in the repo root.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 13:09:34 +01:00
m3tam3re cf1c4b9f31 Merge pull request 'fix(t3code): gitea SSH im Service HOME-unabhaengig machen' (#29) from fix/t3code-ssh-hardening into master
Reviewed-on: #29
2026-10-31 16:46:02 +01:00
m3ta-chiron 56f2295e6e fix(t3code): make gitea SSH access HOME-independent in the service
The T3 threads could clone from gitea interactively (m3tam3re terminal)
but not from the t3code service context. Instead of guessing which link
in the spawn chain drops HOME, make every link irrelevant:

- t3SshConfig: absolute IdentityFile (no ~ resolution needed)
- service env: HOME set explicitly + GIT_SSH_COMMAND pointing at the
  absolute store-path ssh config — git uses exactly this config for
  gitea remotes regardless of HOME or user ssh-config lookup

Verified via nix eval: HOME=/home/m3tam3re and
GIT_SSH_COMMAND=ssh -F /nix/store/...-t3-gitea-ssh-config land in the
unit. After deploy: systemctl restart t3code, then retrigger the clone
thread.
2026-10-31 16:44:15 +01:00
m3ta-chiron 95f5b76629 chore: fix agent-prod 2026-10-31 16:20:18 +01:00
m3tam3re cae0e33625 Merge pull request 'feat(m3-hermes): T3 agent runtime — agent-lib skills + gitea as m3ta-chiron' (#28) from feat/t3code-agent-lib-gitea into master
Reviewed-on: #28
2026-10-31 15:59:27 +01:00
m3ta-chiron e3c3823a46 feat(m3-hermes): T3 agent runtime — agent-lib skills + gitea as m3ta-chiron
- agent-lib v2 client: /etc config + timer sync (2h/on-boot) as m3tam3re,
  deploys work repo into ~/.agents/skills + ~/.config/opencode/*
- Claude Code skills mirror (system path unit, port of m3ta-home
  claude-skills.nix)
- git identity m3ta-chiron via t3code service env (no ~/.gitconfig hijack)
- gitea SSH for m3tam3re (User gitea, key ~/.ssh/gitea) + host key pinned
  system-wide; one-time keygen steps documented in module header
2026-10-31 15:23:58 +01:00
m3tam3re bfd45b81ef Merge pull request 'fix(m3-hermes): firewall.service failed — ip46tables cannot parse IPv4 CIDR' (#27) from fix/firewall-ip46tables into master
Reviewed-on: #27
2026-10-31 13:26:56 +01:00
m3ta-chiron d8239fcd32 fix(m3-hermes): firewall — interface match instead of IPv4 CIDR in ip46tables
The mesh-only accept rules used 'ip46tables ... -s 100.x/16'. ip46tables
runs every rule through iptables AND ip6tables; ip6tables cannot parse an
IPv4 CIDR and aborts with 'host/network not found', failing the whole
firewall.service (status 2).

Consequence beyond the unit failure: the firewall-start script aborted at
the first such rule, so the trailing default-reject rules were never
applied — the input filter was effectively OPEN (only SSH/established
rules had been added). This also explains why the mesh services were
reachable although the previous 100.64.0.0/16 source rule never matched
any peer.

Fix: match on the NetBird interface (-i wt0) instead of a source range —
family-agnostic, survives NetBird range changes, and matches the idiom
the generated script already uses for NetBird service ports. Applied to
ai-memory, hermes-dashboard and t3code rules (add + stop-commands).

After deploying: firewall.service completes, default-reject applies, and
49374/9119/8642/3773 become reachable from the mesh ONLY (previously
open to everyone). Anything that silently relied on the open filter will
start failing — that is the intended posture.
2026-10-31 13:17:42 +01:00
m3tam3re 4e6a193d00 Merge pull request 'feat(m3-hermes): T3 Code cockpit — t3 serve systemd service, mesh-only' (#26) from feat/t3code-cockpit into master
Reviewed-on: #26
2026-10-31 12:12:53 +01:00
m3ta-chiron 275546f0ee fix(t3code): drop gateway symlink — subscription login per harness
Subscription auth (Claude Code, OpenCode) must live in each harness's own
credential store; providers do not allow routing subscriptions through
other tools. The keyless m3ta-gateway stays herdr-worker-only. Both
harnesses now login interactively once after deploy (see module header).
2026-10-31 12:12:06 +01:00
m3ta-chiron c310ce57f4 feat(m3-hermes): T3 Code cockpit — t3 serve systemd service, mesh-only
Three-lane agent setup (interactive cockpit / autonomous workers / Hermes
control lane): T3 Code server runs on m3-hermes as a systemd service under
the m3tam3re user, reachable only from the NetBird mesh (direct pairing,
no T3 Connect cloud relay).

- hosts/m3-hermes/services/t3code.nix: t3 serve on port 3773 (port
  registry), User=m3tam3re, keyless m3ta-gateway opencode config for
  harnesses, claude-code/opencode2 in service PATH
- ports.nix: t3code = 3773
- fix netbirdRange in ai-memory.nix + hermes-dashboard.nix: the fleet
  mesh actually runs in 100.81.0.0/16 (wt0 kernel route), the previous
  100.64.0.0/16 rules never matched any real peer

One-time steps after deploy (documented in the module header):
sudo -u m3tam3re claude auth login; t3 pair for client devices.
2026-10-31 11:18:49 +01:00
m3ta-chiron e965490e66 chore: flake update 2026-10-31 10:59:27 +01:00
m3tam3reandClaude Fable 5.1 1ca2bf0b94 fix(m3-hermes): restart ai-memory when its secret changes
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 14:24:51 +01:00
m3tam3reandClaude Fable 5.1 162f12814a chore(ai-memory): consolidate with glm-5-turbo
GLM-5.3 spent the structured-call output budget on reasoning and got
truncated (finish_reason=length) on every profile classification.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 14:23:45 +01:00
m3tam3reandClaude Fable 5.1 a45e3e184b fix(m3-hermes): seed ai-memory hook credential for Hermes
The native hook command reads <data_dir>/auth-token, not the config's
bearer_token_file; without it every Hermes event was spooled with a 401.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 14:02:31 +01:00
m3tam3reandClaude Fable 5.1 c2601d5e70 chore(ai-memory): drop one-shot initial root password from server secret
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 13:56:13 +01:00
m3ta-chiron 3276020422 Merge feat/ai-memory: central ai-memory server, Hermes wiring, kratos client 2026-10-25 13:55:25 +01:00
m3tam3reandClaude Fable 5.1 3ce4eb74bd chore: bump m3ta-home (session-aware Claude MCP bridge)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 13:36:08 +01:00
m3tam3reandClaude Fable 5.1 919ea49a1e chore: bump m3ta-home (ai-memory client module)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 13:31:55 +01:00
m3tam3reandClaude Fable 5.1 f142cc0721 feat(ai-memory): central agent memory server on m3-hermes
Server: services.ai-memory (upstream NixOS module, llm-agents build) on
m3-hermes, bound to the Netbird range, LLM consolidation via z.ai GLM,
one global cross-project profile, auto-improve proposals gated behind
approval. Traefik on m3-atlas publishes it as memory.m3ta.dev.

Clients: per-host aim_ keys (user "sascha", labels kratos / hermes /
az-lt-nix) as agenix secrets. m3-kratos enables m3ta-home's
coding.aiMemory with the AZ checkouts routed to the "az" workspace.

Hermes: lifecycle hooks, MCP bridge and skills wired declaratively, a
home-workspace marker ("home"/"assistant"), and Honcho replaced by the
built-in notes so ai-memory is the single shared memory.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-25 13:01:05 +01:00
m3ta-chiron 35a0a45977 chore: flake update 2026-10-24 10:01:39 +02:00
m3ta-chiron 8ae524739f chore: flake update 2026-10-22 14:56:23 +02:00
m3ta-chiron 2b2579c2f5 chore: flake update 2026-10-11 16:46:22 +02:00
m3tam3re 6e348eae44 Merge pull request 'feat(m3-hermes): herdr sandbox user + fleet runtime service (R2)' (#25) from feat/herdr-sandbox into master
Reviewed-on: #25
2026-10-11 15:59:54 +02:00
m3ta-chiron b7961b6e4e feat(m3-hermes): herdr sandbox user + fleet runtime service (R2)
- System-User herdr (isSystemUser, /var/lib/herdr, homeMode 750) ohne Fleet-Keys
- systemd herdr-server: User=herdr, StateDirectory 0750, RuntimeDirectory 0700,
  herdr aus llm-agents.herdr (gepinnt über Flake), path= statt PATH-Env
- moshi-hook-herdr Service mit ConditionPathExists (startet erst nach dem
  einmaligen imperativen moshi-hook-Install für den herdr-User)
- Worker-opencode-Config auf keyless m3ta-gateway (NetBird Agent Network,
  Budget-Deckel liegt in der NetBird-Policy)
- Genau EINE Sudo-Regel abwärts: hermes -> herdr, nur /run/current-system/sw/bin/herdr-run *
  (Whitelist: agent|pane|workspace|status|integration)

Eval verifiziert: serviceConfig.User=herdr, home, sudo-Rule, tmpfiles, ConditionPathExists.
Closure-Build vor dem Merge ausfuehren (s. PR-Beschreibung).
2026-10-11 15:06:00 +02:00
m3ta-chiron 9f671e334d fix(flake): unbreak m3-kratos build after flake update
- m3ta-home: point back at ssh remote (drop local path override) and
  update lock to 8987758, which removes the dankBatteryAlerts plugin
  enable (plugin was removed from dms-plugin-registry because battery
  alerts are builtin to DMS stable now; the dangling enable left
  plugins.dankBatteryAlerts.src undefined and broke evaluation)
- nix.nixPath -> nix.settings.nix-path (option was renamed/removed)
- media profile: enable graphics profile flag

Validated via nix build --dry-run of m3-kratos toplevel (eval OK,
367 derivations pending).
2026-10-11 14:29:58 +02:00
m3ta-chiron 972a81f367 flake update 2026-10-04 14:01:45 +02:00
m3ta-chiron 0576b3c60b feat(colmena): passwordless activation via sudoers rules scoped to colmena's exact commands
Colmena connects with BatchMode=yes and no TTY (src/nix/host/ssh.rs),
so a sudo password prompt can never be answered - non-root deploys
REQUIRE NOPASSWD. New extraServices.colmenaDeploy (enabled on all
five hosts) grants m3tam3re passwordless sudo for exactly the two
invocations colmena performs (verified against colmena 0.5/0.6
profile.rs + host/{ssh,local}.rs, default NixFlags are empty):

- /run/current-system/sw/bin/nix-env --profile /nix/var/nix/profiles/system --set /nix/store/*
  (system profile switch, goals switch/boot)
- /nix/store/*/bin/switch-to-configuration <boot|switch|test|dry-activate>
  (activation, exact single argument)

Everything else keeps requiring the sudo password; extraRules sort
after the wheel rules, so last-match-wins keeps the exception scoped.
Also enables passwordless 'colmena apply-local' on the desktops, which
uses the same activation path.

Residual risk (documented in the module): anyone holding the deploy
user's SSH key can activate arbitrary store closures - that is the
deploy capability itself, inherent to NixOS remote activation.

One-time bootstrap per server (rules arrive WITH a deploy, and the
first deploy cannot answer a password prompt):
  nixos-rebuild switch --flake .#m3-atlas --target-host m3tam3re@m3-atlas --use-remote-sudo
2026-10-04 13:42:02 +02:00
m3ta-chiron db0bfbc707 feat(colmena): set up Colmena as deploy tool for all NixOS hosts
- Add colmena flake input (nix-community >= 0.5.0) and CLI to devShell
- Extract shared nixosHosts module map consumed by BOTH
  nixosConfigurations (nixos-rebuild/nh) and the Colmena hive,
  so local rebuilds and remote deploys cannot drift apart
- Add colmenaHive output via colmena.lib.makeHive (direct flake
  evaluation, required on Nix >= 2.21) plus legacy colmena output
- Tags: m3-atlas/m3-helios/m3-hermes = server, m3-ares/m3-kratos =
  desktop with allowLocalDeployment; targetUser m3tam3re
- meta.allowApplyAll = false guards bare 'colmena apply'; use
  'colmena apply --on @server' or 'apply-local' instead
- Document deploy commands in AGENTS.md

Note: colmena builds render system.nixos.version as 26.11pre-git
(colmena's evaluator has no flake sourceInfo) - cosmetic only,
package closures are identical to nixos-rebuild.

Includes pending working-tree changes: hermes-agent bump v2026.9.24,
agent-lib input removal, m3ta-home switched to local path checkout,
m3-kratos monitor setup update, alejandra reformat of rofi-pass.nix.
2026-10-04 13:07:14 +02:00