From fc8de1a5b02d4cfa0a13854d01ea7ddc270a5ad4 Mon Sep 17 00:00:00 2001 From: Hugh Kaznowski Date: Sun, 6 Sep 2026 14:00:05 +0100 Subject: [PATCH] Remove wishlist --- WISHLIST.txt | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 WISHLIST.txt diff --git a/WISHLIST.txt b/WISHLIST.txt deleted file mode 100644 index 7880e8c..0000000 --- a/WISHLIST.txt +++ /dev/null @@ -1,6 +0,0 @@ -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. -