How to use Claude to build a Rust log processor
Kelora is an experimental Rust log processor whose code and tests were generated by Claude CLI and Codex CLI, with the author supplying ideas and reviewing docs.
Prompt to try
Editorial adaptation, not the source author’s exact prompt. Replace bracketed inputs and review tool permissions first.
Help implement [log-processing feature] in [Rust repository]. Discuss the requirements with me, write a specification, then implement the feature with behavior tests, documentation, and CI updates. Provide example logs I can use to evaluate the result.
Reach people exploring AI agents
See placements →What happened
The author describes Kelora as functional and useful, with 1000+ automatic tests passing, but considers it an experiment or prototype rather than established production software.
Reported by dloss on Hacker NewsHow the agent did it
- Discuss log-processing feature ideas with the agents.
- Have the agents write specifications and implementations.
- Generate tests, documentation, and CI with the agents.
Where a person stepped in
The author explicitly does not review code, but uses the program and reviews documentation, and warns that passing automated checks does not establish production suitability.
A person approved each step before the agent continued.
Kelora began as an attempt to rewrite the author's Python log-processing tool, klp, in Rust. The author barely knew Rust and turned the project into an experiment in how far AI-assisted development could go. The supplied post says the code and extensive test suite were generated entirely by Claude CLI and Codex CLI.
The human supplied feature ideas and discussed them with the agents. The agents then wrote specifications, implementations, tests, documentation, and CI. The author's feedback came from using the program and reviewing its documentation rather than reading its code. The resulting command-line tool processes log files and streams, with built-in functions for parsing, transforming, and analysis, plus features including JWT parsing and pseudonymisation.
The author calls the result functional and useful, while explicitly treating it as an experiment or prototype. Passing more than a thousand automatic tests and checks including clippy, cargo audit, cargo deny, and cargo fuzz did not resolve the absence of human code review. The post suggests trying the supplied example logs. Who it's for: programmers exploring agent-generated implementations in a language they are still learning, while retaining responsibility for evaluating the result.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · dloss
Frequently asked questions
Did the author review the generated code?
No. The author says they use the resulting program and review the documentation, but do not review its code.
Which agents generated Kelora?
The post names Claude CLI with Sonnet 4 to 4.5 and Codex CLI with GPT5-codex as generators of the code and extensive test suite.
More details
Remaining steps
- Use the resulting program and review its documentation.
About this account
The agents generated the specifications, implementation, tests, documentation, and CI; the human supplied feature ideas and practical feedback.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=46181970. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: dloss on Hacker News
Source published 7 Dec 2025
Source checked 14 Oct 2026
Tools and topics
Claude CLI · Codex CLI · Rust · clippy · cargo audit · cargo deny · cargo fuzz
AI development
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.