Viewing profile — AmiteK
AmiteK
HN member- Joined
- Mon, Dec 29, 2025, 9:42 AM UTC
- HN karma
- 2
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About AmiteK
Recent public activity
- story
- story
-
comment
Comment #47589332
GitHub: https://github.com/LogicStamp/logicstamp-context It compiles TypeScript codebases into deterministic, structured context. Happy to answer questions.
- story
- story
- story
-
story
Show HN: Detect Drift in TypeScript codebases
I’ve been building LogicStamp Context, an open-source CLI that analyzes TypeScript codebases using the TypeScript AST and compiles them into deterministic JSON “contracts”. These d…
-
story
Show HN: Catching breaking interface changes in TypeScript refactors (AST-based)
I built an open source CLI that analyzes TypeScript codebases using the TypeScript AST (via ts-morph) and extracts structured architectural contracts and dependency graphs. The goa…
-
comment
Comment #46716564
I agree - that’s on me for the wording. I’m not claiming repeatability of agent inference or LLM sessions. By “repeatability” I mean the extraction itself: given the same repo stat…
-
comment
Comment #46716379
I think the disagreement is about where inference belongs, not whether LLMs are capable. Git diffs + LLM inference work well for understanding changes once. What I’m targeting is r…
-
comment
Comment #46716146
That’s a reasonable hypothesis, and I agree LLMs are very good at inferring structure from raw TypeScript within a local reasoning window. However, that inference has to be repeate…
-
comment
Comment #46716074
I think we’re optimizing for different constraints. If your goal is zero extra round trips and you’re happy with AGENTS.md auto-injection + LSP queries, then I agree LogicStamp won…
-
comment
Comment #46716009
On tool-call overhead: in the MCP flow it’s typically 1–2 calls per task (watch_status once, then read_bundle for the relevant slice). In watch mode we also skip snapshot refresh e…
-
comment
Comment #46715939
I think there’s a conflation here between artifact determinism and agent behavior. LogicStamp’s determinism claim is about the generated context: same repo state + config ⇒ identic…
-
comment
Comment #46715921
That’s fair, and I agree LSP-style search is excellent for interactive, local exploration. LogicStamp isn’t trying to replace that. The problem it targets is different: producing s…
-
comment
Comment #46715891
Yes. In the MCP setup the agent doesn’t decide to regenerate arbitrarily. When stamp context --watch is active, the MCP server detects it. The agent first calls logicstamp_watch_st…
-
comment
Comment #46715838
Adding a bit more context since I didn’t see your expanded comment at first: AGENTS.md and LogicStamp aren’t mutually exclusive. AGENTS.md is great for manual, human-curated guidan…
-
comment
Comment #46715826
Good question. LogicStamp treats context as deterministic output derived from the codebase, not a mutable agent-side model. When code changes mid-session, watch mode regenerates th…
-
story
Show HN: Deterministic, machine-readable context for TypeScript codebases
Hi HN, I built a CLI that extracts a deterministic, structured representation of a TypeScript codebase (components, hooks, APIs, routes) directly from the AST. The goal is to produ…
-
story
Show HN: A CLI That Compiles React, Next.js, TS and Vue for LLMs
After working with LLMs on real React/TypeScript codebases, I kept running into issues caused by missing structure - invented props, broken hook assumptions, and style leakage. log…
-
comment
Comment #46429864
I think this distinction matters less to users than to builders. From a user perspective, what’s novel here is policy and intent (no ads, no AI, privacy-first), not whether the ind…
-
comment
Comment #46429836
One thing that seems under-discussed is what kind of state is worth persisting. Raw chat logs are cheap; distilled decisions, constraints, and preferences are harder but much more …