3 ms·

That's what I am talking about as well. The low-level implementation of an agent isn't necessarily a rigid graph, and I'd actually argue its explicitly not this

That's what I am talking about as well. The low-level implementation of an agent isn't necessarily a rigid graph, and I'd actually argue its explicitly not this.

zh2408 2y ago
The current implementations of Agents, e.g., OpenAI agents released last week, are based on graph (workflow): https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/run.py#L119 https://github.com/openai/openai-agents-python/blob/48ff99bb... Not sure about Cursor you mentioned as its agent is not open sourced.
- campbel 2y ago
  This link is also referring to the nodes as agents. So its a system of agents interacting to product an outcome. I'm not saying this system is bad, just that I think it deserves another name rather than calling the whole system an "Agent". It's many agents working in a coordinated fashion.
  - zh2408 2y ago
    No. It's not many agents in the workflow. It's not an agent per node. The whole workflow and the Runner class is for one agent. Check out this line: https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/agent.py#L132 https://github.com/openai/openai-agents-python/blob/48ff99bb... A single `run_agent` is implemented based on the Runner class and workflow. So usually the workflow is for one agent (unless there is handoff).
    - campbel 2y ago
      They define it in the same file https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/agent.py#L27C8-L27C98 https://github.com/openai/openai-agents-python/blob/48ff99bb... > An agent is an AI model configured with instructions, tools, guardrails, handoffs and more. Agents can hand off to other agents, but even the hand-off is decided by the agent itself, not a pre-defined orchestration.

3 ms·

That's what I am talking about as well. The low-level implementation of an agent isn't necessarily a rigid graph, and I'd actually argue its explicitly not this

by campbel 2y ago

That's what I am talking about as well. The low-level implementation of an agent isn't necessarily a rigid graph, and I'd actually argue its explicitly not this.

zh2408 2y ago
The current implementations of Agents, e.g., OpenAI agents released last week, are based on graph (workflow): https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/run.py#L119 https://github.com/openai/openai-agents-python/blob/48ff99bb... Not sure about Cursor you mentioned as its agent is not open sourced.
- campbel 2y ago
  This link is also referring to the nodes as agents. So its a system of agents interacting to product an outcome. I'm not saying this system is bad, just that I think it deserves another name rather than calling the whole system an "Agent". It's many agents working in a coordinated fashion.
  - zh2408 2y ago
    No. It's not many agents in the workflow. It's not an agent per node. The whole workflow and the Runner class is for one agent. Check out this line: https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/agent.py#L132 https://github.com/openai/openai-agents-python/blob/48ff99bb... A single `run_agent` is implemented based on the Runner class and workflow. So usually the workflow is for one agent (unless there is handoff).
    - campbel 2y ago
      They define it in the same file https://github.com/openai/openai-agents-python/blob/48ff99bb736249e99251eb2c7ecf00237488c17a/src/agents/agent.py#L27C8-L27C98 https://github.com/openai/openai-agents-python/blob/48ff99bb... > An agent is an AI model configured with instructions, tools, guardrails, handoffs and more. Agents can hand off to other agents, but even the hand-off is decided by the agent itself, not a pre-defined orchestration.