fix(compiler): thread actor-level system_prompt into graph node metadata #7
Merged
hurui200320
merged 1 commits from 2026-05-22 07:08:20 +00:00
fix/compiler-thread-system-prompt into master
No Reviewers
Labels
Clear labels
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Needs Feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
Currently being processed by an implementer worker.
Currently being processed by the merge driver.
Currently being processed by a reviewer worker.
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
Tracking issues used by the AI Automation system for agents to communicate and report.
Rebase conflict needs LLM conflict-resolver.
Failing CI needs implementer attention.
Documenting a driver incident or rollback.
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Type
Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
aditya (Aditya Chhabra)
aleenaumair (Aleena Umair)
brent.edwards (Brent Edwards)
CoreRasurae (Luis Mendes)
drew (Drew Morris)
eugen.thaci (Eugen Thaci)
freemo (Jeffrey Phillips Freeman)
HAL9000 (HAL 9000)
HAL9001 (HAL9001)
hamza.khyari (Hamza Khyari)
hurui200320 (Rui Hu)
justin.morris
khird (Kyle Hird)
org.cleveragents
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Blocks
#6 compile_actor() drops graph-level system_prompt — not threaded into CompiledActor
cleveragents/cleveractors-core
Reference: cleveragents/cleveractors-core#7
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "fix/compiler-thread-system-prompt"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
compile_actor()silently dropped the actor-levelsystem_promptfield fortype: graphactors. TheCompiledActorcontained no trace of it, forcing host applications to keep the rawActorConfigSchemain scope as a workaround.This fix applies three targeted additions across two files to close both the compilation gap and the runtime context gap.
Motivation
docs/reference/actors_schema.mdexplicitly documentssystem_promptas "Default prompt for graph-level agents" — placing it in the same semantic category asproviderandmodel: actor-level fields that serve as fallback defaults for all AGENT nodes. The compiler already threadedproviderandmodelviasetdefault;system_promptwas simply never added to the same pattern.A second independent gap in
Node._execute_agent()meant that even after fixing the compiler, thesystem_promptvalue would not appear in the context dict passed toagent.process_message().Changes
src/cleveractors/actor/compiler.py_map_node()gains anactor_system_prompt: str | None = Noneparameter.merged_meta.setdefault("system_prompt", actor_system_prompt)is applied inside theif node.type == NodeType.AGENT:block, after the existingprovider/modelcalls.setdefaultpreserves any per-node override inconfig.system_prompt.actor_system_prompt is not None, so actors without a top-levelsystem_promptdon't carry a"system_prompt": Noneentry in every AGENT node's metadata.compile_actor()passesactor_system_prompt=config.system_promptto_map_node().src/cleveractors/langgraph/nodes.pyNode._execute_agent()extractsnode_system_promptfromself.config.metadata.get("system_prompt")and injects it into the context dict beforestate.metadatais merged. This allows host agents to readcontext.get("system_prompt")without a direct reference to the rawActorConfigSchema. Per-executionstate.metadata["system_prompt"]overrides still take precedence.isinstance(raw, str)guard rejects non-string values (e.g. integer, list) that could be injected via manually constructedNodeConfig."system_prompt"is added toignore_keysto prevent agents from mutating it in the context dict and accidentally persisting the mutation intometadata_updates.docs/reference/actor_compiler.mdAGENTrow now references a detailed "AGENT node defaults" subsection describing thesystem_promptthreading behavior.features/compiler_system_prompt.feature+features/steps/compiler_system_prompt_steps.pyTen BDD scenarios covering the full behavioral surface:
system_promptis threaded into each AGENT node'sNodeConfig.metadata.config.system_prompttakes precedence over the actor-level default (setdefault semantics).agent.process_message()receivessystem_promptin its context dict.state.metadata["system_prompt"]overrides the compiled default at runtime.state.metadata["system_prompt"] = Noneoverrides a compiled default (clearing the prompt).system_promptis threaded into AGENT node metadata.system_promptis passed into the runtime context dict.system_promptin compiled metadata.system_promptdoes not add the key to AGENT node metadata (post-review: was "set to None").system_promptis excluded from the runtime context dict.Post-review additions
Step-definition file reorganized into functional sections (compilation assertions, runtime assertions). "Each AGENT node" step definitions include a guard against zero-AGENT-node graphs.
Quality Gates
nox -s lintnox -s typechecknox -s unit_testsnox -s coverage_reportnox -s security_scannox -s dead_codenox -s complexityCloses #6
f4155e489dtoa18e8c5931a18e8c5931tobc01753113bc01753113to5aeadcc0aa5aeadcc0aato61c8a6f48f61c8a6f48ftodd6c20df5dSelf-QA Review — Approved ✅
Ran 2 review/fix cycles. The PR is ready to merge.
Cycle 1 — Request Changes (0C / 3M / 5m / 2n)
All issues were addressed in the same cycle:
system_prompt(compiler + runtime)state.metadata = {"system_prompt": None}runtime overridesetdefault(None)unconditionally polluted AGENT node metadata shapeif actor_system_prompt is not None:metadata.get()returnedAny; no runtime type guardisinstance(node_system_prompt, str)system_promptabsent fromignore_keys— agent mutations leaked to state"system_prompt"toignore_keys# Then steps for new scenarioswas a drafting artifactagent_nodes_found > 0guard addedAfter fixes: 17/17 scenarios, all 7 quality gates ✅
Cycle 2 — Approve (0C / 0M / 3m / 3n)
No further fixes applied. Remaining items are non-blocking:
system_promptin node metadataignore_keysexclusion workssystem_promptoverride combination_CapturingAgentuses shallowdict()copy instead ofdeepcopy"None"edge caseThese can be addressed in a follow-up ticket if desired.
Quality Gates (final)
nox -s lintnox -s typechecknox -s unit_testsnox -s coverage_reportnox -s security_scannox -s dead_codenox -s complexityhurui200320 referenced this pull request2026-06-12 03:13:59 +00:00