Gateway mode runs CLIver as a long-running daemon with cron scheduling, a web admin portal, and platform adapters for messaging services.
Architecture
Section titled “Architecture”┌─────────────────────────────────────┐│ Gateway Daemon ││ ││ ┌──────────┐ ┌──────────────────┐ ││ │ Cron │ │ Control Server │ ││ │ Scheduler│ │ (Unix Socket) │ ││ └──────────┘ └──────────────────┘ ││ ││ ┌────────────────────────────────┐ ││ │ Platform Adapters │ ││ │ Slack ... │ ││ └────────────────────────────────┘ ││ ││ ┌────────────────────────────────┐ ││ │ AgentCore │ ││ └────────────────────────────────┘ │└─────────────────────────────────────┘Starting the Gateway
Section titled “Starting the Gateway”# Install gateway dependenciespip install cliver[gateway]
# Start the daemoncliver gateway start
# Check statuscliver gateway status
# Stopcliver gateway stopCron Scheduling
Section titled “Cron Scheduling”The gateway’s cron scheduler runs tasks on a schedule. Tasks are defined with a schedule field and executed by their own AgentCore instance.
# Create a scheduled taskcliver task create daily-summary \ --prompt "Summarize today's activity from the logs" \ --schedule "0 9 * * *"
# List taskscliver task list
# Run a task immediatelycliver task run daily-summaryPlatform Adapters
Section titled “Platform Adapters”Gateway exposes AgentCore through messaging platforms. Each adapter handles message routing, permission prompts, and session management for its platform.
Currently tested: Slack.