J. Zane Cook

I was able to override this for my own session by running `unset ARGV0` Wherever it is setting the `ARGV0` is where the issue starts. What is the purpose of...

I believe these changes would not be a standard agent protocol SDK that's 1:1 with the spec. For changes to the spec, there needs to be an RFC written out...

Hey @nalbion, can you take a look at the Python SDK? The way it implements the task_handler is by using a `Task` class, rather than specifying the task_id and task_input...

> It would be create to have a "hello world"-like example too. An Echo-example for example. The example for the Python SDK (here https://github.com/AI-Engineers-Foundation/agent-protocol-sdk-python/blob/main/examples/minimal.py) is essentially an echo example. I...

> This is a very important and simple pull request, so why hasn't it been merged yet? I haven't been maintaining this repo, we haven't been having meetings. Normally we...

@wilsonianb @hackgoofer Please take a look when you get a chance :+1:

I believe we've settled on the following format for a route existing at `/ap/v1/agent/info`: ```json { "name": "My Agent", "description": "General purpose agent.", "version": "1.0.0", "protocol": "1.0", "github": "https://github.com/myagent/myagent", "url":...

Additionally to this schema we discussed having a `config_options` array of objects with the properties of type, default, description,and options (optional). Where type refers to the type of input, and...

Here is the AgentInfo object I had been thinking of using for the spec: ```yml AgentInfo: type: object properties: name: description: Name of the agent. type: string example: My Agent...

> * Rename `additional_input` to `config`; > * Add an `info` endpoint Reference Issue #39 for more on these topics. > plugin (that allows agent developers to specify their own...