I'm using linkding: https://linkding.link/.
It works great. It has a minimal set of features and can be self-hosted.
I'm paying pikapods to host it for me, but if I needed to, I can switch to doing it on my own.
Readit Newsjasonriddle commented on Best Practices for Building Agentic AI Systems userjot.com/blog/best-pra... · Posted by u/vinhnx
So far I've been hardcoding these into the API calls.
Sure, but to clarify, so you are probably setting temperature to close to 0 in order to try to get as consistent output as possible based on the input? Have you made any changes to top k and/or top p that you have found makes agents output more consistent/deterministic?
jasonriddle commented on Best Practices for Building Agentic AI Systems userjot.com/blog/best-pra... · Posted by u/vinhnx
When you say "same output" in
> Every subagent call should be like calling a pure function. Same input, same output. No shared memory. No conversation history. No state.
How are you setting temperature, top k, top p, etc?
jasonriddle commented on Show HN: JMAP MCP – Email for your agents github.com/wyattjoh/jmap-... · Posted by u/wyattjoh
Nice! I have been searching for something like this for while!
jasonriddle commented on Rethinking CLI interfaces for AI notcheckmark.com/2025/07/... · Posted by u/Bogdanp
This is a great post, thank you for sharing. I like the idea of giving hints to the LLMs.
To clarify, the example that was provided using `command_not_found_handler`, is that possible to implement in bash? Or perhaps you were saying this would be a nice to have if this functionality existed?
@simonw, how much have you used Claude code? I'm wondering if it makes sense to use Claude code as the main driver, but have crafted specialized "llm" based tools for Claude to use.
I would love to only have to use llm, but with the amount of functionality that Claude code provides, it seems unlikely that llm would ever support all of its features. Also, I have realized that llm is narrower in scoop, which is something I like about the tool.
Wouldn’t Intuit do the same?
Yes,
https://www.intuit.com/privacy/statement/
>> How we share your personal information
> For mergers and acquisitions. If we are involved with a merger, asset sale, financing, liquidation, bankruptcy, or the acquisition of all or part of our business to another company, we may share your personal information with that company and its advisors before and after the transaction date.
That sounds like a disclaimer for something that is true for every company, no?
But unlike every other company, this company has your most sensitive tax information. For some that's fine, but others might not like that.
FreeTaxUSA only cost me like… $20? in California this year and had very little upsells. Highly recommend!
Just so that you are aware, TaxHawk (which owns and operates FreeTaxUSA) may choose to sell your information in the event of a "business transition" (bankruptcy, merger, etc)
From https://www.freetaxusa.com/privacy
>> Business transitions
> In the event TaxHawk evaluates or conducts a business transition whether as a going concern or as part of bankruptcy, liquidation, or similar proceeding, such as a merger, being acquired by another company, or selling a portion of its assets, the personal information of users will, in most instances, be part of the assets transferred. Users will be notified, via email and/or through a prominent notice on the FreeTaxUSA.com website, 30 days prior to a change of ownership or control of their personal information.
My main concern with these browser agents are how are they handling prompt injection. This blog post on Perplexity's Comet browser comes to mind: https://brave.com/blog/comet-prompt-injection/.
Also, today Anthropic announced Claude for Chrome (https://www.anthropic.com/news/claude-for-chrome) and from the discussion on that (https://news.ycombinator.com/item?id=45030760), folks quickly pointed out that the attack success rate was 11.2%, which still seems very high.
How do you plan to handle prompt injection?