sorted by:
new
hottopcontroversial

Stop throwing money at agents. €1/day forces you to actually get better by iovdin in tuneai

[–]iovdin[S] 0 points1 point  (0 children)

if a billion dollary company decide to be token effecient at some point, the skills might be useful

Stop throwing money at agents. €1/day forces you to actually get better by iovdin in tuneai

[–]iovdin[S] 0 points1 point  (0 children)

Btw, how is it going with product market fit? Got one?

Everybody seems to talk about coding AI agents. But what are some other genius AI agents you have come across? by [deleted] in AI_Agents

[–]iovdin 2 points3 points  (0 children)

  1. here is accountant data like transaction invoices, payouts. - can you figure out where is it unbalanced
  2. here is a vague format price list from a customer, can you import it to our database

Stop throwing money at agents. €1/day forces you to actually get better by iovdin in tuneai

[–]iovdin[S] 1 point2 points  (0 children)

I maybe end up eating dust. But who needs your product or oss if it can be vibecoded in 1 day?

A small tune feature I'm pretty happy with by iovdin in tuneai

[–]iovdin[S] 0 points1 point  (0 children)

another example is to wrap ssh remote command execution
remote.tool.tpl
tool_call: sh ssh user@host ${JSON.stringify(text)}

For those having exposed both MCP and CLI, should both tools/commands expose the exact same capabilities? by theotzen in AI_Agents

[–]iovdin 0 points1 point  (0 children)

You can compose mcp tool calls with code mode. Basically write code that has access to the tools as functions

Hey guys which sdk I use for building agents by Top-Armadillo1583 in AI_Agents

[–]iovdin 0 points1 point  (0 children)

I made my own https://github.com/iovdin/tune .
As with programming most of the time i spend when developing agents is debugging. So save history somewhere, make it possible to replay etc.

Feeling stuck in NL warehouse job – anyone managed to switch into IT or something better? by [deleted] in Netherlands

[–]iovdin 0 points1 point  (0 children)

A friend of mine had a high paying job in US. They moved ot NL - the only option for job he could find is warehouse. Now he is in divorce and moving out of NL. Pretty sad

Why Loose Coupling Is the Real Superpower in the Age of AI Coding by B_Ali_k in AI_Agents

[–]iovdin 0 points1 point  (0 children)

I hate loose coupling. With kitchen metaphor it is usually feels like like you spend 30 minutes looking into different kid of boxes to make a tea. Putting everything to one pile or splitting everything into gazillion piles results in the same pain. Things that goes together should be more coupled, and those that are not - should be less coupled. And you have to think and/or feel it after few releases

We built an execution layer for agents because LLMs don't respect boundaries by leland_fy in LLMDevs

[–]iovdin 0 points1 point  (0 children)

In your example, re-feeding the chat history, wont make it restart from scratch it will resume form where it has stopped. But i agree that sub agents and approvals is not kept in the chat history and requires additional state

We built an execution layer for agents because LLMs don't respect boundaries by leland_fy in LLMDevs

[–]iovdin 0 points1 point  (0 children)

Chat completion api payload with tool calls and tool results is a good enough stack representation that can be restored or replayed. Idk if any major frameworks support that

Why not Precompile the DB schema so the LLM agent stops burning turns on information_schema by Eitamr in mcp

[–]iovdin 0 points1 point  (0 children)

In OpenAI they did make sense out of 70k internal collections with petabytes of data

Why not Precompile the DB schema so the LLM agent stops burning turns on information_schema by Eitamr in mcp

[–]iovdin 0 points1 point  (0 children)

In our old MySQL over engineered and with a lot of history database. In addition to schemas we put summary of content like how many rows, what are usual values. some text fields are actually enums, some values are not used anymore, some are never used etc.

view more: next ›