Comments URL: https://news.ycombinator.com/item?id=48516365

Points: 2

# Comments: 0

But from what I hear, Fable looks like an incremental update, with improved behavior imprinted by training.

Something that you could theoretically approximate by using a good set of instructions and model orchestration (tweaking the session life cycle, using a second model to understand user intentions, using a third model to prevent drift, ...).

If the above is true, the only discriminator would be user effort.

If Fable is dangerous, then we are still in danger right now, and have been for the last few months at the very least.

- they "swallowed" my monthly subscription in January, I had to subscribe (and pay again)

- they promised tools to preview the new costs, they did too little and too badly (you have to click an export button, wait for a mail and click on a link on it, then download their csv which even showed substantial dollar costs for rows with 0 requests)

- models kept on appearing/disappearing/re-appearing-disabled on our company account in the latest weeks

- as of May 31th, I had no clue and could not tell if I would been migrated to token billing, or would have to stay with the moronic new multipliers. News came on Jun 1st, of course

They don't really look able or willing to properly manage their own product at the moment. And yes, new subscription are paused, so I won't be able to re-subscribe.

Quite frankly the only reason to go copilot is to have it in the VSCode chat (and yes, there's some chance to use it BYOK, provided it works).

Besides, their offering even at market prices looks inferior to what you can get elsewhere. You can use DeepSeek and pay pennies, use Fireworks and have the choice to use cheaper open models (which GitHub does not provide, and are actually good and even better than Claude sometimes), or subscribe to Open Router and use virtually anything.

I still have no idea if cancelling my subscription will get any money back, probably not.

I paused taking that momentarily out of precaution while I wait some physical issue to normalize, but I plan to resume it in some weeks. Also it is considered a very safe supplement.

`Error: JavaScript modules found but libperry_jsruntime.a not found. Build it with: cargo build --release -p perry-jsruntime`

Turns out jsruntime was removed one week ago, but the error messages probably not have been updated as they should.

https://github.com/PerryTS/perry/commit/848339fa4ee4b00a53f5...

We actually need more of this, perhaps not in this exact shape, but similar.

It would be extremely cool to be able to write one or two lines of prompt in my harness, and have a light model iterate with me a few times writing/proposing requirements, guidelines and explanations, refining the prompt until it's ready to be sent to the actual LLM.

Lack of specifications in the prompt is (imho?) one of the main drivers that lead the LLMs astray, and it often happens because it's not realistic to always type or even thing every angle before submitting each prompt.

Think of it as the missing link between a single-shot prompt and a skill.

It should be ideally integrated in the chat, for quick access.

This project is probably different in aim, but I still find it interesting.

1. it's behind a login wall | 2. tries to download its own OpenCode instead of using the one installed on my machine

I also tried to create a new workspace. It asked what I want to do. I tried with "create user accounts", and it proceeded to create the git worktree (without asking for its name) and sent that prompt straight to OpenCode without allowing me to choose the LLM model.

I plaud the effort - I really do - but it doesn't really seems a great experience for now.

And in my experience is not that much faster to start than more complex software like Visual Studio Code.

Comments URL: https://news.ycombinator.com/item?id=48117574

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47618498

Points: 1

# Comments: 0

> `includeCoAuthoredBy`: whether to instruct the agent to add a Co-authored-by trailer to git commits; defaults to `true`.

This means that, if you don't explicitely configure otherwise, the LLM is specifically instructed to include co-authorship in its higher level instructions.