Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agent Is Not the Model

code.joejag.com

Post reply on HN
Print view View original

11–20 of 38 posts

Re: Agent Is Not the Model

#11

Post by altmanaltman »

ericol wrote: post #2

On other news, water wets. > I often hear people use the words agent and model interchangeably _what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive. > to help us have more precise conversations. What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitp…

Wait, your entire comment is on how one should not nitpick someone's mental models but isn't that you nitpicking at someone's mental models? sus

Re: Agent Is Not the Model

#12

Post by yipinwong »

ericol wrote: post #2

On other news, water wets. > I often hear people use the words agent and model interchangeably _what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive. > to help us have more precise conversations. What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitp…

You sound like a manager, not an engineer.

Re: Agent Is Not the Model

#14

Post by llm_nerd »

I've literally never heard anyone conflate an agent and a model. Ever.

Often with posts like this I imagine someone had their own confusion and then somehow projected it on everyone else. Like Trump thinking people didn't know about the word groceries or that dumb ends with a b.

Re: Agent Is Not the Model

#15

Post by yipinwong »

rwoerz wrote: post #8

> An agent system is made up of several layers. Why "layers"? The constituents of a Multi-agent System (MAS) [1] are called "agents". BTW: Synecdochical semantic diffusion is not uncommon in software engineering [1] https://en.wikipedia.org/wiki/Multi-agent_system

Real-life usage of interchangeable or synecdochical word triumphs in real life.

My take on the post is for engineering disciple where JoeJag wants to create a common word while tackling "Agent" issues.

I like Joe's approach as this disambiguates during troubleshooting without trying to figure out under which "context" other engineers are using Agent vs. Models.

You get lost in context just like AIs do without such disambiguation.

Re: Agent Is Not the Model

#16

Post by mickmister »

ericol wrote: post #2

On other news, water wets. > I often hear people use the words agent and model interchangeably _what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive. > to help us have more precise conversations. What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitp…

> _what_ people.

Eric from alignment and research at OpenAI: https://www.youtube.com/watch?v=87DyyMV0kCY

It honestly bothers me so much when he says "This new model has access to x". No, the harness you allowed it use at runtime has access to x.

Re: Agent Is Not the Model

#17

Post by agentdev001 »

The post ends with a comment on "its not about being pedantic..." so, a few not being pedantic bits:

In the table "Real world examples";

"Claude Desktop" houses three harnesses at the moment; Claude, Claude Cowork, and Claude Code.

"Claude CLI", I presume, is referring to Claude Code CLI. This is distinct from the 'ant CLI', which is sometimes referred to as 'Claude CLI'.

"Cursor" could be any of them- but, 'Cursor Agents', 'Cursor Cloud Agents', 'Cursor CLI', and whatever the vscode fork is called now, are distinct. Maybe not in the context of this blog post, but it isnt specified which is being referred to in the example table.

"ChatGPT" sounds like the chatgpt web interface. OpenAI's desktop app is named 'ChatGPT Desktop', and now houses 'ChatGPT work' and 'Codex' (Codex Desktop, not the TUI, though it does essentially wrap the tui and give it capabilities through app-built-in tools). I believe the ChatGPT web interface's harness can change a bit, depending on settings + subscription level (remote sandboxes, etc.) Additionally, there is a distinction in available models depending on which "ChatGPT" product is being used (instant/live/etc non-5.6 luna/terra/sol suite).

Inference service is more accurately 'default inference provider'.

Also, this post has an ai-generated smell.

Re: Agent Is Not the Model

#18

Post by joejag »

agentdev001 wrote: post #17

The post ends with a comment on "its not about being pedantic..." so, a few not being pedantic bits: In the table "Real world examples"; "Claude Desktop" houses three harnesses at the moment; Claude, Claude Cowork, and Claude Code. "Claude CLI", I presume, is referring to Claude Code CLI. This is distinct from the 'ant CLI', which is sometimes referred to as 'Claude CLI'. "Cursor" could be any of them- but, 'Cursor A…

Author here. My writing process is:

* Write: Use FluidVoice to get all the text down in my own voice

* Edit: Ask ChatGPT etc to criticise the article

* Cleanup: Grammarly

* Publish: Good old GitHub Pages

Re: Agent Is Not the Model

#19

Post by yomismoaqui »

mickmister wrote: post #16
ericol wrote: post #2

On other news, water wets. > I often hear people use the words agent and model interchangeably _what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive. > to help us have more precise conversations. What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitp…

> _what_ people. Eric from alignment and research at OpenAI: https://www.youtube.com/watch?v=87DyyMV0kCY It honestly bothers me so much when he says "This new model has access to x". No, the harness you allowed it use at runtime has access to x.

You can argue that the model has access to that tool through the harness the same way your brain has access to see this comment through your body (your eyes specifically).
Post reply on HN