letsbe-sysadmin

Commit Graph

Author	SHA1	Message	Date
Matt	2d27775a2c	fix: Persist credentials across container and orchestrator restarts Build and Push Docker Image / build (push) Successful in 1m56s Details Previously, the agent would clear credentials on ANY heartbeat failure, causing infinite re-registration loops when: - Agent container was updated while orchestrator was running - Orchestrator was restarted while agent was running Changes: - Add HeartbeatStatus enum and HeartbeatResult dataclass - Modify heartbeat() to return status info instead of just bool - Only clear credentials on 401/403 (AUTH_FAILED) - Keep credentials on transient errors (NETWORK_ERROR, SERVER_ERROR) - Handle AUTH_FAILED in heartbeat_loop() for mid-session invalidation Scenarios now handled: - Agent restart: keeps creds, retries until orchestrator responds - Orchestrator restart: keeps creds, retries with backoff - Admin deletes agent: clears creds, breaks out for re-registration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-09 15:25:44 +01:00
Matt	51b3050b5c	feat: add secure registration with credential persistence - Add REGISTRATION_TOKEN config for new secure registration flow - Add agent_secret and credentials_path config options - Update HTTP client to use X-Agent-Id/X-Agent-Secret headers - Add credential persistence to ~/.letsbe-agent/credentials.json - Load persisted credentials on startup to survive restarts - Verify credentials via heartbeat before skipping registration - Maintain backward compatibility with legacy Bearer token auth The agent now: 1. First tries to load persisted credentials 2. Validates them via heartbeat 3. Falls back to registration if invalid/missing 4. Persists new credentials after successful registration 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-07 11:11:59 +01:00
Matt	b351217509	Initial commit: SysAdmin Agent with executors - Core agent architecture with task manager and orchestrator client - Executors: ECHO, SHELL, FILE_WRITE, ENV_UPDATE, DOCKER_RELOAD, COMPOSITE, PLAYWRIGHT - EnvUpdateExecutor: Secure .env file management with key validation - DockerExecutor: Docker Compose operations with path security - CompositeExecutor: Sequential task execution with fail-fast behavior - Comprehensive unit tests (84 tests) - Docker deployment configuration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-03 11:05:54 +01:00

Author

SHA1

Message

Date

Matt

2d27775a2c

fix: Persist credentials across container and orchestrator restarts

Build and Push Docker Image / build (push) Successful in 1m56s Details

Previously, the agent would clear credentials on ANY heartbeat failure,
causing infinite re-registration loops when:
- Agent container was updated while orchestrator was running
- Orchestrator was restarted while agent was running

Changes:
- Add HeartbeatStatus enum and HeartbeatResult dataclass
- Modify heartbeat() to return status info instead of just bool
- Only clear credentials on 401/403 (AUTH_FAILED)
- Keep credentials on transient errors (NETWORK_ERROR, SERVER_ERROR)
- Handle AUTH_FAILED in heartbeat_loop() for mid-session invalidation

Scenarios now handled:
- Agent restart: keeps creds, retries until orchestrator responds
- Orchestrator restart: keeps creds, retries with backoff
- Admin deletes agent: clears creds, breaks out for re-registration

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-09 15:25:44 +01:00

Matt

51b3050b5c

feat: add secure registration with credential persistence

- Add REGISTRATION_TOKEN config for new secure registration flow
- Add agent_secret and credentials_path config options
- Update HTTP client to use X-Agent-Id/X-Agent-Secret headers
- Add credential persistence to ~/.letsbe-agent/credentials.json
- Load persisted credentials on startup to survive restarts
- Verify credentials via heartbeat before skipping registration
- Maintain backward compatibility with legacy Bearer token auth

The agent now:
1. First tries to load persisted credentials
2. Validates them via heartbeat
3. Falls back to registration if invalid/missing
4. Persists new credentials after successful registration

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-07 11:11:59 +01:00

Matt

b351217509

Initial commit: SysAdmin Agent with executors

- Core agent architecture with task manager and orchestrator client
- Executors: ECHO, SHELL, FILE_WRITE, ENV_UPDATE, DOCKER_RELOAD, COMPOSITE, PLAYWRIGHT
- EnvUpdateExecutor: Secure .env file management with key validation
- DockerExecutor: Docker Compose operations with path security
- CompositeExecutor: Sequential task execution with fail-fast behavior
- Comprehensive unit tests (84 tests)
- Docker deployment configuration

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-03 11:05:54 +01:00

3 Commits