Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

arps18.github.io

Post reply on HN
Print view View original

91–100 of 297 posts

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#91

Post by redhale »

new_account_101 wrote: post #57
redhale wrote: post #37

Earlier quoted context omitted.

Just use a fallback, like Codex CLI. Takes a little effort upfront to ensure your configuration is wired correctly for both harnesses, but it is pretty easy to get them 90% identical (there will almost always be some experimental / edge case features that differ across harnesses, but in my experience those are negligible in practice).

[flagged]

I more meant feature-level differences. For instance, Claude Code has agent teams, and Codex CLI does not. Or for a while, Codex had "/goal" and Claude Code did not (though now Claude Code has it too). To your point, it is usually possible to polyfill these gaps either with custom code/skills/hooks or with third party plugins.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#93

Post by sshine »

aqme28 wrote: post #53
sshine wrote: post #13

The number one power move I have is Nix integration. The availability of tooling, secrets, environment and the ability for the agent to modify its own environment is... well, I don't know how people live without it. I guess you guys still install things using commands and hope everything you need is present on the next machine? Developer machine, CI environment, deployment environment: They're all derived from a sing…

I just gave mine its own VPS. Maybe more expensive than Nix but it was very easy

I also prefer giving it a VPS over a Docker container.

On my own machine I just give it a Linux User Namespace, i.e. soft virtualisation via "bubblewrap."

What Docker Compose and Linux User Namespaces provide that a VPS doesn't: You can easily mount extra directories from your developer host machine in read or read+write mode. With the VPS you (most likely) need it to clone all of your resources separately, which requires SSH keys, and now you're slowly building towards an independent agentic environment, which is definitely very nice, but time-consuming, compared to piggybacking on your developer environment. Definitely the direction I'm going.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#94

Post by sshine »

professor_v wrote: post #52
sshine wrote: post #13

The number one power move I have is Nix integration. The availability of tooling, secrets, environment and the ability for the agent to modify its own environment is... well, I don't know how people live without it. I guess you guys still install things using commands and hope everything you need is present on the next machine? Developer machine, CI environment, deployment environment: They're all derived from a sing…

I just use docker and I don't feel I'm missing anything?

Docker's ability to mount host directories in the container is really nice.

Maybe you have some premade tooling that helps provide persistency between container invocations.

But by default, closing your agent container and opening it again just wipes everything you didn't host-mount.

What I'm advocating is really just the same functionality without the Docker runtime, because Linux has namespaces.

Feels more like you're on your host system with exactly the minor variations you specify.

Making Docker feel like your host system is possible, but I just never felt at home.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#95

Post by lukan »

alexwwang wrote: post #86
downsplat wrote: post #78

I've been using Claude to work on a medium-sized (100+kLoc) codebase, and it's a great productivity multiplier. Putting hours into creating a good AGENTS file is more improved results a lot. I find that over time it picks up the codebase quite well. Tedious tasks that would take a day are now a matter of a few prompts. Still... I'm not ready to give it more autonomy. Even as it gets high-level things quite well, I st…

Understandable. You don’t want to lose control to your codebase and don’t trust LLM is competent in handling that fully.

No. Because they still hallucinate at times. Confuse things. Forget things. Or none of the above, as it is anthropomorphizing, but the result is the same. They can make incredible working one shots, you start to trust them, then you trust too much and .. feel the result.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#96

Post by thunky »

netdevphoenix wrote: post #10

What happens when you have a codebase made with claude using this setup and claude is down for let's say 8 hours? Are you able to efficiently, smoothly and productively take over the codebase?

What happens if you get up in the morning and your car won't start? Do you walk to work?

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#97

Post by voqv »

sshine wrote: post #94
professor_v wrote: post #52

Earlier quoted context omitted.

I just use docker and I don't feel I'm missing anything?

Docker's ability to mount host directories in the container is really nice. Maybe you have some premade tooling that helps provide persistency between container invocations. But by default, closing your agent container and opening it again just wipes everything you didn't host-mount. What I'm advocating is really just the same functionality without the Docker runtime, because Linux has namespaces. Feels more like you…

yeah, you can use rocker --home --user -- $CI_IMAGE

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#98

Post by Zetaphor »

netdevphoenix wrote: post #10

What happens when you have a codebase made with claude using this setup and claude is down for let's say 8 hours? Are you able to efficiently, smoothly and productively take over the codebase?

A local model doesn't have downtime. No you can't be as hands off with it as something like Claude, but isn't that a good thing?

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#99

Post by alexwwang »

lukan wrote: post #95
alexwwang wrote: post #86

Earlier quoted context omitted.

Understandable. You don’t want to lose control to your codebase and don’t trust LLM is competent in handling that fully.

No. Because they still hallucinate at times. Confuse things. Forget things. Or none of the above, as it is anthropomorphizing, but the result is the same. They can make incredible working one shots, you start to trust them, then you trust too much and .. feel the result.

Yes. I am fighting with the disobeyance of LLM on working through my pipeline commands. I believe these violations are caused by its hallucinations. So I am still developing a mechanical system to monitor agents’ behaviors automatically. I believe these routines and monitors will play as a set of scaffold to keep leading the LLM on the right way all the time.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#100

Post by blululu »

The author’s claim that Claude is a multiplier for skill is probably true for now but it also feels like cope inspired by usability issues with Claude. The advice is all good, but none of it is especially clever or impressive or hard to grasp. The multiplier just comes from the fact that anthropic hadn’t taken this essay and several similar ones and incorporated their feedback into the product. This is a pretty shallow most of expertise that anthropic ought to automate in a week.
Post reply on HN