5 ms·
My dream tooling is for every tool to have an terminal interface so that I can create comprehensive megabooks to get all the context that lives in my head. i.e.
by pm90 1y ago
My dream tooling is for every tool to have an terminal interface so that I can create comprehensive megabooks to get all the context that lives in my head. i.e. jira, datadog, github etc, all in one pane.
- buremba 1y agoYou might like MCP then.
- x-complexity 1y ago> You might like MCP then. That's entirely different to what's being desired by GP. > > My dream tooling is for every tool to have an terminal interface so that I can create comprehensive megabooks to get all the context that lives in my head. i.e. jira, datadog, github etc, all in one pane. My perspective on this is essentially having jira/datadog/github/etc be pluggable into the CLI, and where standard bash commands & pipes can be used without major restrictions. (Something akin to Yahoo Pipes) MCP is highly centered around LLMs analyzing user requests & creating queries to be run on MCP servers. What's being desired here doesn't centralize around LLMs in any sense at all.
- janwandersun 1y ago[dead]
- omneity 1y agoIt’s actually not too far off. Yes MCP is designed for LLM interactions, but we observed that it’s an invocation API that’s pretty generic. So we built a package format that encapsulates computations and makes them accessible from any of MCP, REST, JSON-RPC over WS (the generic cousin of MCP).. We build logic once and make it automatically accessible from any of these consumption methods, in a standardized way to our clients, and I am indeed piping some of these directly in the CLI to jq and others for analysis.
- turtlebits 1y agoNot sure what you mean- github and datadog already have official CLI tools.
- trenchgun 1y agoJira has official CLI as well https://appfire.atlassian.net/wiki/spaces/JCLI/overview https://appfire.atlassian.net/wiki/spaces/JCLI/overview and plenty of unofficial ones
- prakashn27 1y agoThis is not an official API, this is from third party. stop promoting appfire products as official api.
- tecleandor 1y agoMaybe something like wtfutil? (Although wtf development has been stuck for a year, but I guess that's the general idea...) https://wtfutil.com/ https://wtfutil.com/
- rochak 1y ago+1. Personally, I’m a fan of TUIs too that make things a bit more user friendly. Just imagine an internal TUI framework that has components for each internal service that you can lego-build into personalised TUI dashboard. Hmm, seems like something I could work on the side at work. Would be a huge undertaking but very interesting.
- pm90 1y agoYes this is what I was thinking. This is how terraform became the lingua franca of iac, I was hoping that something like this would happen with TUIs too, so instead of all vendors creating their own bespoke cli, they all implemented a plugin of some generic TUI framework.
- npodbielski 1y agoIMHO just an API would be enough, tool could be written on top of that. My ideal world would be every service, tool and application to have API that I can use i.e. if fridge is open too long (API polling or API webhook) I can send roomba to close it (using API of roomba). Because why not?! World of API...