HackerTrans
トップ新着トレンドコメント過去質問紹介求人

blas0

no profile record

投稿

[untitled]

1 ポイント·投稿者 blas0·4 か月前·0 コメント

[untitled]

1 ポイント·投稿者 blas0·6 か月前·0 コメント

Show HN: Klaus – a Claude Code native delegating agentic harness

1 ポイント·投稿者 blas0·6 か月前·1 コメント

The Abstraction Trap: Why Layers Are Lobotomizing Your Model

2 ポイント·投稿者 blas0·6 か月前·2 コメント

Claude-quill your inline parallel coderabbit

github.com
1 ポイント·投稿者 blas0·6 か月前·1 コメント

(part 2) unsevering Claude to my codebase, attempting persistent memory

2 ポイント·投稿者 blas0·7 か月前·0 コメント

Continuous Architectural Memory

github.com
3 ポイント·投稿者 blas0·7 か月前·1 コメント

コメント

blas0
·6 か月前·議論
Good evening!

Here is something pretty cool that I encountered during a personal project session...

https://github.com/blas0/deterministic-invocation-of-subagen...

---

Deterministically invoke subagents within the same Claude session (using the Claude Max plan) -- meaning no API or agent SDK!

--

Pretty cool find tbh, not sure if i'm late to the party or what - I havent found anything in regards to my findings/anything similar.

Let me know all yall's thoughts!
blas0
·6 か月前·議論
claude-quill:

Intent verification for AI-pilled devs

We've all been there. You ask Claude for a login form with Zod validation, it ships something that looks right, you move on. Three files later you realize...no Zod anywhere. The vibes were immaculate but the implementation was mid.

Built a hook-based daemon that shadows Claude Code sessions. Captures your original intent, watches every Write/Edit, then runs a review agent that actually checks if the code matches what you asked for. Catches yolo implementations before they compound into tech debt.

Zero config. Just hooks. Findings get injected back into context so Claude fixes its own mistakes.

https://github.com/blas0/claude-quill

Think of it as a mini-inline code rabbit, parallel with your sessions agents.

Excited to see contributions.
blas0
·7 か月前·議論
CAM (Continuous Architectural Memory) solves an architectural problem:

CAM addresses a fundamental LLM limitation; statelessness. Each session starts fresh. Claude Hooks became the architectural driver to solve this.

The mechanism: Claude Hooks intercept operations (UserPromptSubmit, PostToolUse, SessionEnd, etc.) and feed data into CAM—code changes, tool use patterns, research, prompts, plans. CAM embeds everything, builds relationships, and injects relevant context before Claude processes requests. Allowing contextually aware planning, tool use, researching, diagnosing, debugging, implementations, etc.

The result: an infinitely updated, persisted codebase map + documentation source. CAM reads/writes/iterates/revises/queries/validates research and tool use across sessions, compounding context awareness over time.

This pattern generalizes beyond Claude. Any LLM integration with hooks can gain persistent memory this way.

Open source MVP. Uses Gemini embeddings, SciPy clustering, knowledge graphs.

https://github.com/blas0/Severance