a2aproject / a2aproject/a2a-python

[Bug]: `taskId` without `contextId` creates a new context instead of inheriting it

Open
#1,206 3 comments 0 reactions 1 assignee Claimed by @rohityan View on GitHub
component: server status:awaiting response status:stale
Dominant language
Python
Stars
2.1k
Forks
496
Avg merge
4d 17h
Merged PRs (30d)
12

Description

### What happened?

Spec:
> Agents MUST infer contextId from the task if only taskId is provided

Code:
```python
request_context = await self._request_context_builder.build(
params=params,
task_id=original_task_id,
context_id=original_context_id,
task=None,
context=call_context,
)
```

Then further...
```
if not self._context_id and not self._params.message.context_id:
self._params.message.context_id = self._context_id_generator.generate(...)
```

I found no sight of using the task's context, it seems to generate it anyway. But please correct me if I'm wrong.

### Relevant log output

```shell

```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.