lev-os/agentping

記録された最新のソース活動: 2026年2月11日 14:08

SkillsMP カタログ更新: 2026年11月2日 18:02

収集済み skills: 1

GitHub スター: 4
GitHub フォーク: 0

AI アシスタントでインストール

このプロンプトをコピーして、使用中の AI アシスタントに送ってください。

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/lev-os/agentping.

リポジトリの README

README の元ファイル：README.md

README の元ファイルを読む

README 全文を表示

# AgentPing AgentPing is an AI-native interaction protocol: agents emit structured intent, and humans respond through rich action surfaces instead of plain chat. ## What This Product Is AgentPing is built around one idea: - Any action surface can be an AgentPing surface. That includes: - web apps - desktop apps - browser extension surfaces - mobile surfaces (including iOS/Swift adapters) - chat channels (Telegram, Slack, Discord) Chat is supported, but it is not the primary UX model. ## Current State (2026-02-11) What is working now in this repo: - Hexagonal core domain (`@agentping/core`) with ports and adapters - Dashboard runner control plane (`dashboard-runner` + `dashboard-manager-server`) - Active UI surfaces: - Studio Storybook (`:6006`) - Sofia/UI-kit Storybook (`:6007`) - web-ui (`:5173`) - canvas (`:5174`) - dashboard-manager-ui (`:5175`) - studio web shell (`:5180`) - Canonical canvas payload is Sofia-first for render pings - Fail-fast theme contract in Studio/web-ui: `agentping | skynet | syslog` and `light | dark` Known consolidation gaps: - Duplicate canvas/renderer logic still exists across packages - Adapter-owned component trees still exist outside `packages/ui` - Studio still has embedded dashboard orchestration paths alongside runner/server ## End-State Goals 1. One UI kit (`packages/ui`) as shared source of primitives. 2. One canvas implementation with explicit modes. 3. One dashboard control plane (runner + manager server only). 4. Strict fail-fast config (no hidden theme/mode fallback). 5. Open-source adapter model so new channels are easy to build. ## Immediate Handoff Scope Current dev handoff focuses on three items: 1. Make Sofia primitives generic (remove aviation/domain-bound naming from canonical shared components). 2. Enforce single component library ownership in `packages/ui`. 3. Execute GenUI upgrades against target architecture while clearly labeling temporary current-state exceptions. ## Open-Source Adapter Vision The target developer experience: - install AgentPing core/runtime packages - implement one adapter contract - render AgentPing primitives in your surface (browser extension, SwiftUI, Telegram, etc.) - receive typed action callbacks back to your agent runtime Design principle: - strong primitives + typed contracts + deterministic rendering This is the base needed for voice-driven generative UI where chat is secondary. ## Quick Start (Consolidated Runtime) ```bash pnpm install pnpm -r build pnpm dashboards:kill pnpm dashboards:start pnpm dashboards:status ``` In another terminal, run protocol daemon: ```bash pnpm --filter @agentping/daemon dev ``` ## Docs Map - Primary handoff narrative: - `docs/architecture.md` - UI companion: - `docs/web-ui-architecture.md` - Consolidation handoff: - `docs/handoff-consolidation.md` - `docs/open-questions.md` - Runtime + commands: - `docs/getting-started.md` - Component inventory: - `docs/component-catalog.md` - GenUI research and implementation specs: - `docs/genui/readme.md` ## Project Structure ```text / ├── packages/ │ ├── core/ # Domain Logic (No External Dependencies) │ ├── daemon/ # Main Orchestrator & HTTP Server │ ├── studio/ # Electron Desktop GUI │ ├── canvas/ # Shared React Component Library │ ├── api-client/ # Typed HTTP Client SDK │ ├── dashboard-runner/ # Process Management for External Apps │ ├── dashboard-manager-server/ # Dashboard HTTP + WebSocket Server │ ├── dashboard-manager-ui/ # Dashboard React Web UI │ └── adapters/ │ ├── web-ui/ # React + Vite Web Interface │ ├── mcp/ # Claude/Cursor MCP Integration │ ├── http-api/ # REST + WebSocket API Layer │ ├── storage-sqlite/ # SQLite Persistence (Pure JS) │ ├── cli/ # Terminal Interface │ ├── slack/ # Slack Notification Channel │ ├── webhook/ # HTTP Webhook Delivery │ ├── browser-extension/ # Chrome Extension (CDP Bridge) │ └── ext-apps/ # MCP UI Extensions (SEP-1865) └── docs/ # Architecture & ADRs ``` ## GenUI Relationship Thesys/C1 reverse-engineering artifacts are promoted into `docs/genui/` as research + implementation inputs. Important: - `docs/genui/` contains candidate patterns and design direction. - Runtime truth and cutover rules are defined in `docs/architecture.md` (primary), with UI-boundary detail in `docs/web-ui-architecture.md` (companion).

リポジトリの README を読み込んでいます…

このリポジトリの skills

ウェブ開発者

1 件の職業カテゴリ · 100% 分類済み

skill

職業分類

説明

更新

agentping-playground

ウェブ開発者

Generate interactive playgrounds for AgentPing components

原文の言語: 英語

2026-02-11

収集済み skill 1 件中 1 件を表示しています。