- having to hand-roll CLI test commands

- remembering custom project commands & arguments

- adding test time only logs (timings, cache invalidations or other useful markers)

What I wanted:

- UI experience navigating and running the tests tree

- easy and fast access to custom task commands (xtask)

- test time only events that get generated regardless of global log level

And so I built (with the help of Codex..) Nextdeck. https://github.com/romansky/nextdeck

I tested Nextdeck to work with iTerm2 & Terminal & Intellij's built-in terminal.

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

Points: 2

# Comments: 0

While working on big Rust projects I'm experiencing these pains: - having to hand-roll CLI test commands - remembering custom project commands & arguments - adding test time only logs (timings, cache invalidations or other useful markers)

What I wanted: - UI experience navigating and running the tests tree - easy and fast access to custom task commands (xtask) - test time only events that get generated regardless of global log level

And so I built Nextdeck. https://github.com/romansky/nextdeck

I tested Nextdeck to work with iTerm2 & Terminal & Intellij's built-in terminal.

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

Points: 1

# Comments: 0

This is a project I've been working on since the beginning of 2025 full time, without funding.

Coding agents have fundamentally changed the way we write software. When you let an agent write code, pull dependencies, and run scripts, you are delegating trust while still keeping the responsibility. You shouldn't have to choose between moving fast with agents and maintaining basic control over your host machine.

Normally, we just inspect the final result, treating the app like a black box. Most security tools only sandbox the app runtime and ignore the build phase.

CapaKit is my attempt to make agent-driven development safe and productive.

Secrets baked into config, dependencies installed with full host access, and arbitrary scripts running during `npm install` are all things you need to take into account.

I started working on CapaKit in early 2025 (originally as mcpgate.com) after Anthropic announced MCP. As the agent ecosystem started to standardize, I wanted to apply what I've learned building with LLMs since GPT-3. Building real AI apps turns out to be really hard: lots of moving parts, from security to devops, on top of a fast-moving ecosystem.

What is special about CapaKit?

CapaKit sandboxes the entire app lifecycle, not just the running code- building, testing, and running, all first class citizens of usability and security.

What that means concretely: - Per-app policies with workload-level isolation. - No inherited host environment, no broad filesystem access. - No network by default — outbound traffic has to be explicitly allowed. - Ephemeral, single-use sandboxes for every build and run. - Secrets resolved on demand instead of hardcoded.

Security with awesome usability: you can upload your AI app Kits to Github and anyone can run them with a single command:

capakit run https://github.com/capakit/hello-world-demo-kit

CapaKit is currently macOS only and is free to use.

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

Points: 6

# Comments: 1

To your q, I make huge effort in making my prompts as small as possible (to get the best quality output), I go as far as removing imports from source files, writing interfaces and types to use in context instead of fat impl code, write task specific project / feature documentation.. (I automate some of these with a library I use to generate prompts from code and other files - think templating language with extra flags). And still for some tasks my prompt size reaches 10k tokens, where I find the output quality not good enough

This specific case worked well, I suspect, since LLMs have a LOT of previous knowledge with HTML, and saw multiple impl and parsing of HTML in the training.

Thus I suspect that in real world attempts of similar projects and any non well domain will fail miserably.

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

Points: 2

# Comments: 0

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

Points: 7

# Comments: 2

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

Points: 1

# Comments: 0

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

Points: 582

# Comments: 46

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

Points: 3

# Comments: 0

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

Points: 2

# Comments: 0

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

Points: 2

# Comments: 0

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

Points: 4

# Comments: 0

Would be really helpful if you opened an issue in Github with a specific example, happy to look into that!