This repository has been archived on 2026-06-13. You can view files and clone it, but cannot push or open issues or pull requests.
anvillm/services/systemd
Levi Neely 50ae1d0dad Add approval gates: beads schema, Conductor, notification daemon, init scripts
Implements bd-i4h (Approval Gates / Human in the Loop):

beads schema (bd-i4h.4):
- Add StatusPendingApproval/StatusPendingReview local status constants
- Add pending-approval, pending-review, resume ctl commands
- Add agent/beads/pending read endpoint
- Document requires-approval/requires-review label conventions
- Update BEADS.md with full Approval Gates section

Conductor bot (bd-i4h.2):
- Read context prompt from stdin when not a terminal (custom prompt support)
- Extend default prompt with approval gate workflow instructions

Human notification daemon (bd-i4h.1):
- Add scripts/anvillm-inbox-notify: streams agent/events, fires notify-send
  for configurable message types (default: APPROVAL_REQUEST, REVIEW_REQUEST)
- Add services/inbox-notify-runit/: runit service
- Add services/systemd/anvillm-inbox-notify.service: systemd user service
- Add services/sysvinit/anvillm-inbox-notify: SysV LSB init script
- Add services/sysvinit/rc.anvillm-inbox-notify: Slackware rc script

anvilsrv init scripts:
- Add services/sysvinit/anvilsrv: SysV LSB init script
- Add services/sysvinit/rc.anvilsrv: Slackware rc script

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-02-22 18:47:23 +01:00
..
README.md feat: split monolith into anvilsrv daemon and Assist client 2026-02-14 11:30:57 +01:00
anvillm-inbox-notify.service Add approval gates: beads schema, Conductor, notification daemon, init scripts 2026-02-22 18:47:23 +01:00
anvilsrv-user.service feat: split monolith into anvilsrv daemon and Assist client 2026-02-14 11:30:57 +01:00
anvilsrv.service feat: split monolith into anvilsrv daemon and Assist client 2026-02-14 11:30:57 +01:00
anvilsrv@.service feat: split monolith into anvilsrv daemon and Assist client 2026-02-14 11:30:57 +01:00

README.md

systemd Service Units for anvilsrv

This directory contains systemd service unit files for running anvilsrv as a system service.

Service Files

Run anvilsrv as a user service using systemd's user instance.

Installation:

# Copy the service file
mkdir -p ~/.config/systemd/user
cp services/systemd/anvilsrv-user.service ~/.config/systemd/user/

# Reload systemd user daemon
systemctl --user daemon-reload

# Enable and start the service
systemctl --user enable anvilsrv-user.service
systemctl --user start anvilsrv-user.service

# Check status
systemctl --user status anvilsrv-user.service

Management:

  • Start: systemctl --user start anvilsrv-user
  • Stop: systemctl --user stop anvilsrv-user
  • Restart: systemctl --user restart anvilsrv-user
  • Status: systemctl --user status anvilsrv-user
  • Logs: journalctl --user -u anvilsrv-user -f
  • Disable: systemctl --user disable anvilsrv-user

Enable Linger (Start on Boot):

To make the service start on system boot even when not logged in:

sudo loginctl enable-linger $USER

2. anvilsrv@.service - System Service Template

Run anvilsrv as a system service for specific users.

Installation:

# Copy the service file
sudo cp services/systemd/anvilsrv@.service /etc/systemd/system/

# Reload systemd daemon
sudo systemctl daemon-reload

# Enable and start for a specific user (replace 'username')
sudo systemctl enable anvilsrv@username.service
sudo systemctl start anvilsrv@username.service

# Check status
sudo systemctl status anvilsrv@username.service

Management:

  • Start: sudo systemctl start anvilsrv@username
  • Stop: sudo systemctl stop anvilsrv@username
  • Restart: sudo systemctl restart anvilsrv@username
  • Status: sudo systemctl status anvilsrv@username
  • Logs: sudo journalctl -u anvilsrv@username -f
  • Disable: sudo systemctl disable anvilsrv@username

3. anvilsrv.service - Simple System Service

Basic system service (less flexible than the template).

Installation:

# Edit the service file to set the correct username
nano services/systemd/anvilsrv.service

# Copy the service file
sudo cp services/systemd/anvilsrv.service /etc/systemd/system/

# Reload systemd daemon
sudo systemctl daemon-reload

# Enable and start the service
sudo systemctl enable anvilsrv.service
sudo systemctl start anvilsrv.service

# Check status
sudo systemctl status anvilsrv.service

Choosing the Right Service

  • User Service (anvilsrv-user.service): Best for most users. Runs in your user session, easier to manage, no sudo required.
  • System Service Template (anvilsrv@.service): Good for multi-user systems or when you need system-level control.
  • Simple System Service (anvilsrv.service): Basic system service, less flexible.

Troubleshooting

Check Logs

# User service
journalctl --user -u anvilsrv-user -n 50

# System service
sudo journalctl -u anvilsrv@username -n 50

Verify Service is Running

# User service
systemctl --user status anvilsrv-user

# System service
sudo systemctl status anvilsrv@username

Check if anvilsrv is Actually Running

anvilsrv status

Restart After Code Changes

# User service
systemctl --user restart anvilsrv-user

# System service
sudo systemctl restart anvilsrv@username

Notes

  • The service automatically restarts on failure with a 5-second delay
  • PID file is cleaned up on service stop
  • Logs are available via journalctl
  • The service uses the anvilsrv binary from ~/bin/anvilsrv