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.

   1. the LLM is instructed on how to write a commit message and never include co-authorship
   2. the LLM is asked to produce a commit message
   3. the LLM output is parsed by a script which removes co-authorship if the LLM chooses to include it nevertheless

Much easier:

    { action: 'help' }

    { action: 'projects.help' }

    { action: 'projects.get', payload: { id: xxxx-xx-x } }

There are other interesting capabilities though, like built in permissions based on HTTP verb, that might be useful to someone.

I don't think what I am doing is really original, but it's shaping nicely.

I am working on:

- feature folders (one folder per feature, with changelog, issues, summaries etc)

- coworkers (cli-agents, with session management)

- agents intra-response messaging

In general the goal is forcing Claude to behave, which is quite ambitious :).

agents role (Orchestrator, QA etc.), agents communication, thinking patterns, iteration patterns, feature folders, time-aware changelog tracking, prompt enforcing, real time steering.

We might really need a public Wiki for that (C2 [1] style)

[1]: https://wiki.c2.com/

I am looking to that exact concept - for a different mean - to develop my agent orchestration hobby project.

LLM working in a «feature folder» where it stores change-logs, documentation, summaries, requirements, attachments, and so on. What I will be looking into very soon, is also storing the session id, for summarisation, history context, and so on.

I will definitely steal some concept from your project.

It's worth noting thet just by setting the right tone of voice, choosing the right words, and instructing it to be concise, surgical in what it says and writes, things change drastically - like night and day.

It then starts obeying, CRITICALs are barely needed anymore and the docs it produces are tidy and pretty.

The LLM instructed to run the initialization script as the first thing, before reasoning about the use request (this proved tricky to achieve). The scripts greps the content matter out of the skill files, along with the file path.

I have no clue if this outperforms an embedded index.

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

Points: 2

# Comments: 0

I really think that helpfulness is a double-edged sword. Most of the mistakes I've seen Claude make are due to it trying to be helpful (making up facts, ignoring instructions, taking shortcuts, context anxiety).

It should maybe try to be open, more than helpful.

Write a good AGENTS.md (or CLAUDE.md) and you'll see that code is more idiomatic. Ask it to keep a changelog. Have the LLM write a plan before starting code. Ask it to ask you questions. Write abstraction layers it (along with the fellow humans of course) can use without messing with the low-level detail every time.

In a way you have to develop a framework to guide the LLM behavior. It takes time.