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

Open

#1,206 opened on Aug 25, 2026 3 comments 0 reactions 1 assignee View on GitHub

@rohityan is already working on this.

Since Aug 25, 2026.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 65/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Domain: backend-api-design

Research direction

Look at the _request_context_builder.build method and the _context_id_generator.generate logic in the codebase. The issue is about context inheritance when only a taskId is provided. Start by finding where task context is fetched and how it should be passed to the message. Check the spec for the exact inference rule. Run existing tests related to task and context creation to see the current behavior.

Written by the indexing model from the issue text.

Description

component: server status:awaiting response status:stale

What happened?

Spec:

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

Code:

        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

Code of Conduct

I agree to follow this project's Code of Conduct

Dominant language: Python
Stars: 2.2k
Forks: 496
Avg merge: 2d 6h
Merged PRs (30d): 19

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[essnmx] Fix typo in NXLauetof application definition Open

essnmx good first issue

Difficulty 1/5 Under an hour Newbie friendliness 95/100

scipp/ess#760 · Opened Sep 23, 2026
[Feature] 奇物选择添加优先级 Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

syfoud/Simulated_Scepter#174 · Opened Sep 23, 2026
garak adapter grades a NaN detector score as PASS Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Giskard-AI/giskard-oss#2840 · 1 comment · Opened Sep 23, 2026
A claim comment carrying the issue number is silently declined while the workflow reports success Open

area: repo bug perceived difficulty: 2

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Nitjsefnie-Harness-Commons/daedalus#926 · Opened Sep 23, 2026
`IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

yeti-platform/yeti#1380 · Opened Sep 23, 2026

More Python issues