[Feature request]: Fabric CLI has become too cluttered

[ksylvan]

What do you need?

From @mattjoyce

[...] About the conceptual weight of the CLI.

It has grown, but it can’t just keep growing by adding more flags to fabric forever.

What I’m really asking for is a stable core shape:

One opinionated default, a small number of sharp options, and something I can actually hold in my head.

If Fabric wants to expand, I’d rather see it grow like a tree:

a clean trunk (patterns / vars / contexts / sessions / model + stdin→stdout)

and then branches as subcommands or extensions (ingest, media, serve, etc).

Otherwise --help turns into a reading session

[mattjoyce]

I have a been having a bit of think.
Setting aside the effort, impact to existing uses and risks of significant refactoring.

I we started again, how would we make it.
If an LLM is a black box function, then Input->LLM->Output , with some function tuning properties, or CLI preferences.
Input here include all the context shaping prior to the request

Fabric has Acquire->Input->LLM->Output
Acquire is like web scraping, you tube, transcriptions, etc and arguably these are not core, and are sometimes 3rd party services.
Maybe there would be true plugins, users would install fabric-youtube, fabrix-webscraperOfChoice

Default Acquire is stdin or file.

Most other options and flags are Input (preparing context) or Output. (or LLM tuning)

I think it would be fun to reimagine the commands as either Verb Noun (List Model, List Patterns) or Noun Verb (Pattern List, Pattern Update)

@ksylvan how much desire for this?

[petterreinholdtsen]

To fit my own need, I created https://codeberg.org/pere/hraesvelgr/ which is a simple python script reusing the patterns from Fabric and only supporting the OpenAI JSON API protocol. Perhaps something for you to have a look at if you want something simpler?

[bdmorin]

have you seen the web interface? I just discovered it and it's amazing.

[ksylvan]

@bdmorin I'm glad you think so. I've been updating and maintaining it.

At the same time, I aim to address @mattjoyce's complaint/wish. I'm incubating ideas to simplify the tangle of CLI arguments.

[dpan]

a TUI would be awesome

[ksylvan]

@bdmorin I fixed a recent bug in the Web UI just now. As a result of some (I'm guessing recent) changes - the chat interface was completely broken - all AI responses were showing up as single words on a line by themselves.

See #2028 and #2029

[ksylvan]

@bdmorin Also added a Vendor dropdown to filter the list of models by vendor as well as updating to the latest versions of Svelte, etc.