agent-service

Manage AI agent sessions via hub-based JSON-RPC methods.

1|1|Updated Mar 5, 2026

Search Tags:#architecture #session-management #websocket #json-rpc #pty #hub #agentd

Ready to run

npx skills add https://github.com/dokipen/claude-cadence --skill agent-service

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-service
Source: https://github.com/dokipen/claude-cadence/tree/main/.gemini/skills/agent-service
Command: npx skills add https://github.com/dokipen/claude-cadence --skill agent-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing AI agent sessions and their lifecycle is complex without a centralized hub. This Skill provides a clear, hub-based approach to orchestrate agentd sessions via WebSocket/JSON-RPC, reducing integration friction and improving visibility.

Core Features & Use Cases

Hub-driven session management: create, monitor, and terminate sessions across multiple agent profiles.
RPC surface: supports createSession, getSession, listSessions, destroySession, and getTerminalEndpoint to control and introspect agents.
Terminal access coordination: retrieve terminal endpoints or relay terminal IO through the hub for seamless interaction.

Quick Start

Install the hub integration and start a session with createSession using an agent_profile.

Frequently Asked Questions about agent-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage multiple AI agent sessions through a centralized hub?▼

You can manage multiple AI agent sessions through a centralized hub by using a hub-based agentd interface. This approach supports WebSocket and JSON-RPC protocols to create, monitor, and terminate sessions across various agent profiles.

What JSON-RPC methods are available for agent session orchestration?▼

The JSON-RPC methods available for agent session orchestration include createSession, getSession, listSessions, destroySession, and getTerminalEndpoint. These methods control and introspect agents via the hub interface.

Do I need a specific configuration to start coordinating agentd sessions?▼

Yes, you need a defined hub.url configuration to start coordinating agentd sessions. You apply this to environments coordinating multiple agent profiles and monitoring states across agents.

What is the best way to monitor and terminate active agent profiles?▼

The best way to monitor and terminate active agent profiles is through hub-driven session management. By applying a centralized hub, you gain visibility to easily introspect states and destroy sessions using JSON-RPC.