phughk/ottyl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Resolve tickets 067-069: named sessions, MCP server, embedded SKILL.md

Browse Source 
Adds a sessions/<name>.json registry (068) so a running ottyl instance can
be discovered by name; an `ottyl mcp --session <name>` subcommand (067)
that starts a short-lived MCP server over stdio (via the official rmcp
SDK), proxying query_logs/declare_param/declare_metric/create_dashboard/
add_panel/get_dashboard tool calls onto the existing HTTP API; and a
SKILL.md (069), embedded into the binary and served at GET /SKILL.md, that
documents how an agent connects to and drives a running instance.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A1ZJ3SrayzLzVndhVq9BmS
This commit is contained in:
Hugh Kaznowski
2026-09-06 13:57:30 +01:00
co-authored by Claude Sonnet 5
parent de9ba6f01b
commit c77404ba4e
8 changed files with 1093 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
WISHLIST.txt
+6
View File
@@ -0,0 +1,6 @@
Ottyl should have an CLI json-rpc mcp functionality. It should allow agents to read or count logs matching queries, create parameters, create metrics, and create dashboards and panels in the dashboards. They should also be able to read dashboards as response data.
Ottyl CLI is aware of sessions, because each session will be stored in the settings location. Since the ottyl service knows it's binding, it can write there `{port}.json` files in say `sessions/` where the settings are. Then ottyl CLI can find sessions there by name and connect to them. Each session of ottyl is named, either via cli clap params, or randomly using the petnames crate.
There should be a SKILL.md file, accessible from ottyl (so embedded like the frontend is) which explains how to interact with ottyl instances for agents. It should be clear and direct without using too many words.