feat(application): support credential injection in ReactiveCleverAgentsApp #128

Merged

CoreRasurae merged 1 commit from feature/application-credential-injection into master 2026-08-10 10:48:32 +00:00

Conversation 3 Commits 1 Files changed 6 +300

CoreRasurae commented 2026-08-09 23:21:08 +00:00

Member

Copy link

Summary

Adds an optional credentials: dict[str, dict[str, str]] | None parameter to ReactiveCleverAgentsApp.__init__, forwarded to the internal AgentFactory(...) built by load_configuration() (ADR-2026 per-request credential injection, already used by create_executor/Executor).

Previously ReactiveCleverAgentsApp — the library's documented "Quick start" entry point — had no way to supply an api_key/base_url for a non-native provider (anything outside openai/anthropic/google, Actor Configuration Standard §4.4.1, e.g. openai_compatible), so any agent using one failed with ConfigurationError: Unsupported provider: ... as soon as it was invoked. create_executor/Executor already supported credential injection but lacked this class's agent-template resolution and config validation, forcing a choice between the two entry points' feature sets. This closes that gap.

• ReactiveCleverAgentsApp.__init__ accepts and validates credentials.
• load_configuration() forwards it to the internal AgentFactory(...).
• Omitting credentials (default) leaves standalone/CLI-mode behavior unchanged.

Test plan

• New Behave scenario: constructs ReactiveCleverAgentsApp with credentials for an openai_compatible agent and asserts successful run_single_shot() execution against a mocked chat model (features/credential_injection.feature, features/steps/credential_application_steps.py).
• nox -s lint — green
• nox -s format -- --check — green
• nox -s typecheck — green (Pyright strict, zero suppressions)
• nox -s security_scan — green (bandit + semgrep + vulture)
• nox -s dead_code — green
• nox -s unit_tests — green (3019 scenarios passed, 0 failed)
• nox -s integration_tests — green (352 Robot tests passed)
• nox -s coverage_report — 96.6% (threshold 96.5%)
• nox -s build — green

Closes #123

## Summary Adds an optional `credentials: dict[str, dict[str, str]] | None` parameter to `ReactiveCleverAgentsApp.__init__`, forwarded to the internal `AgentFactory(...)` built by `load_configuration()` (ADR-2026 per-request credential injection, already used by `create_executor`/`Executor`). Previously `ReactiveCleverAgentsApp` — the library's documented "Quick start" entry point — had no way to supply an `api_key`/`base_url` for a non-native provider (anything outside `openai`/`anthropic`/`google`, Actor Configuration Standard §4.4.1, e.g. `openai_compatible`), so any agent using one failed with `ConfigurationError: Unsupported provider: ...` as soon as it was invoked. `create_executor`/`Executor` already supported credential injection but lacked this class's agent-template resolution and config validation, forcing a choice between the two entry points' feature sets. This closes that gap. - `ReactiveCleverAgentsApp.__init__` accepts and validates `credentials`. - `load_configuration()` forwards it to the internal `AgentFactory(...)`. - Omitting `credentials` (default) leaves standalone/CLI-mode behavior unchanged. ## Test plan - [x] New Behave scenario: constructs `ReactiveCleverAgentsApp` with credentials for an `openai_compatible` agent and asserts successful `run_single_shot()` execution against a mocked chat model (`features/credential_injection.feature`, `features/steps/credential_application_steps.py`). - [x] `nox -s lint` — green - [x] `nox -s format -- --check` — green - [x] `nox -s typecheck` — green (Pyright strict, zero suppressions) - [x] `nox -s security_scan` — green (bandit + semgrep + vulture) - [x] `nox -s dead_code` — green - [x] `nox -s unit_tests` — green (3019 scenarios passed, 0 failed) - [x] `nox -s integration_tests` — green (352 Robot tests passed) - [x] `nox -s coverage_report` — 96.6% (threshold 96.5%) - [x] `nox -s build` — green Closes #123

CoreRasurae added this to the v2.1.0 milestone 2026-08-09 23:21:08 +00:00

CoreRasurae added the

Type

Feature

label 2026-08-09 23:22:12 +00:00

CoreRasurae added a new dependency 2026-08-09 23:22:53 +00:00

#123 ReactiveCleverAgentsApp has no credentials param, so non-native providers (openai_compatible) can never work through it

hurui200320 requested changes 2026-08-10 06:54:06 +00:00

Dismissed

hurui200320 left a comment

Copy link

PR Review: !128 (Ticket #123)

Verdict: Request Changes

The implementation is correct and minimal, but the new BDD scenario does not actually verify that credentials are forwarded through ReactiveCleverAgentsApp to the internal AgentFactory. Because the chat-model builder is fully mocked, the test would pass even if the forwarding were omitted. This is a test-quality issue that must be addressed before approval.

Critical Issues

None.

Major Issues

• Test does not validate credential forwarding (features/steps/credential_application_steps.py, lines 72–91)
  The When step patches cleveractors.agents.llm.build_chat_model to return a mock unconditionally. Since the mock bypasses the real Unsupported provider: openai_compatible logic in llm_client.py, the scenario would succeed even if ReactiveCleverAgentsApp did not pass credentials to AgentFactory. This makes the test tautological with respect to the bug being fixed.
  • Add assertions that app.agent_factory.credentials contains the injected openai_compatible entry and/or that the created LLMAgent received the provider-specific credentials slice.
  • Add a negative scenario that constructs ReactiveCleverAgentsApp without credentials for the same config and asserts it fails with ConfigurationError: Unsupported provider: openai_compatible.

Minor Issues

• Feature-specific step file naming (features/steps/credential_application_steps.py)
  The new steps are used only by features/credential_injection.feature. CONTRIBUTING.md BDD guidelines prefer extending a step file named after the feature (e.g., credential_injection_steps.py) rather than adding another component-specific file, unless the project has an explicit convention to split by subsystem. Verify this is intentional.
• Incomplete constructor validation (src/cleveractors/core/application.py, lines 69–116)
  ReactiveCleverAgentsApp.__init__ only checks that credentials is a dict or None. It does not validate the nested dict[str, dict[str, str]] shape. AgentFactory catches this later during load_configuration, but the public constructor should fail fast on malformed inner values. Consider calling validate_credentials_structure (or an equivalent check) at construction time.
• Missing interactive-session coverage
  Issue #123's acceptance criteria mention both run_single_shot() and start_interactive_session(). The new scenario only covers run_single_shot(). Add coverage for the interactive path.
• Documentation not updated
  README.md and docs/guides/reasoning-aware-llm-agents.md still frame ReactiveCleverAgentsApp as unable to accept credentials. Update the quick-start/guide examples to show the new optional parameter.

Nits

• Class docstring Attributes list in src/cleveractors/core/application.py does not mention the new credentials attribute.
• The temporary directory created with tempfile.mkdtemp() in features/steps/credential_application_steps.py (line 53) is never cleaned up; consider registering a cleanup.

Summary

The code change is exactly what ticket #123 asks for: an optional credentials parameter on ReactiveCleverAgentsApp, forwarded to AgentFactory, with unchanged standalone behavior when omitted. The changelog entry is accurate. However, the new Behave scenario is too weak to protect against regressions. Strengthen the assertions so they verify that the credentials reach the factory/agent, add the missing negative and interactive scenarios, and then this PR is ready to approve.

## PR Review: !128 (Ticket #123) ### Verdict: Request Changes The implementation is correct and minimal, but the new BDD scenario does not actually verify that `credentials` are forwarded through `ReactiveCleverAgentsApp` to the internal `AgentFactory`. Because the chat-model builder is fully mocked, the test would pass even if the forwarding were omitted. This is a test-quality issue that must be addressed before approval. ### Critical Issues None. ### Major Issues - **Test does not validate credential forwarding** (`features/steps/credential_application_steps.py`, lines 72–91) The `When` step patches `cleveractors.agents.llm.build_chat_model` to return a mock unconditionally. Since the mock bypasses the real `Unsupported provider: openai_compatible` logic in `llm_client.py`, the scenario would succeed even if `ReactiveCleverAgentsApp` did **not** pass `credentials` to `AgentFactory`. This makes the test tautological with respect to the bug being fixed. - Add assertions that `app.agent_factory.credentials` contains the injected `openai_compatible` entry and/or that the created `LLMAgent` received the provider-specific credentials slice. - Add a negative scenario that constructs `ReactiveCleverAgentsApp` **without** `credentials` for the same config and asserts it fails with `ConfigurationError: Unsupported provider: openai_compatible`. ### Minor Issues - **Feature-specific step file naming** (`features/steps/credential_application_steps.py`) The new steps are used only by `features/credential_injection.feature`. `CONTRIBUTING.md` BDD guidelines prefer extending a step file named after the feature (e.g., `credential_injection_steps.py`) rather than adding another component-specific file, unless the project has an explicit convention to split by subsystem. Verify this is intentional. - **Incomplete constructor validation** (`src/cleveractors/core/application.py`, lines 69–116) `ReactiveCleverAgentsApp.__init__` only checks that `credentials` is a `dict` or `None`. It does not validate the nested `dict[str, dict[str, str]]` shape. `AgentFactory` catches this later during `load_configuration`, but the public constructor should fail fast on malformed inner values. Consider calling `validate_credentials_structure` (or an equivalent check) at construction time. - **Missing interactive-session coverage** Issue #123's acceptance criteria mention both `run_single_shot()` and `start_interactive_session()`. The new scenario only covers `run_single_shot()`. Add coverage for the interactive path. - **Documentation not updated** `README.md` and `docs/guides/reasoning-aware-llm-agents.md` still frame `ReactiveCleverAgentsApp` as unable to accept credentials. Update the quick-start/guide examples to show the new optional parameter. ### Nits - Class docstring `Attributes` list in `src/cleveractors/core/application.py` does not mention the new `credentials` attribute. - The temporary directory created with `tempfile.mkdtemp()` in `features/steps/credential_application_steps.py` (line 53) is never cleaned up; consider registering a cleanup. ### Summary The code change is exactly what ticket #123 asks for: an optional `credentials` parameter on `ReactiveCleverAgentsApp`, forwarded to `AgentFactory`, with unchanged standalone behavior when omitted. The changelog entry is accurate. However, the new Behave scenario is too weak to protect against regressions. Strengthen the assertions so they verify that the credentials reach the factory/agent, add the missing negative and interactive scenarios, and then this PR is ready to approve.

CoreRasurae force-pushed feature/application-credential-injection from b0b7696e2d to 9101063cbd 2026-08-10 08:27:09 +00:00 Compare

CoreRasurae commented 2026-08-10 08:28:00 +00:00

Author

Member

Copy link

Thanks for the review @hurui200320 — addressed in the amended commit (force-pushed, same branch):

Major

• Test tautology: fixed. The positive scenario now asserts app.agent_factory.credentials["openai_compatible"] actually matches the injected dict (not just that a mocked chat model responded). Added a negative scenario (no credentials, real/unmocked build_chat_model) confirming standalone mode still rejects openai_compatible with Unsupported provider: ... — unchanged behavior, verified rather than assumed.

Minor

• Interactive-session coverage: added, mirroring the single-shot scenario (mocks input/print, feeds one prompt then exit).
• Docs: added a credentials example to README's Quick start and a cross-reference in docs/guides/reasoning-aware-llm-agents.md.
• Step-file naming: checked against the repo's own convention — credential_injection.feature already splits steps across 15+ subsystem-named files (credential_executor_steps.py, credential_factory_steps.py, credential_llm_error_steps.py, etc.). credential_application_steps.py follows that established pattern, so left as-is (matches your own caveat: "unless the project has an explicit convention to split by subsystem").
• Deep constructor validation: intentionally not added. Issue #123 explicitly asks this parameter to mirror Executor's existing credentials handling, and Executor.__init__ itself only does the shallow isinstance(..., dict) check (deep structural validation lives solely in AgentFactory via validate_credentials_structure, shared to avoid duplicating that logic). Adding deep validation only on this entry point would diverge from the mirrored design and duplicate validation the factory already performs. Also added a scenario for the constructor's own non-dict-credentials rejection, since coverage showed that branch wasn't actually exercised.

Nits

• Docstring Attributes list: added credentials.
• tempfile.mkdtemp() cleanup: left as-is — every other step file creating scenario temp dirs in this repo (dozens of them) follows the same no-cleanup pattern, so adding it only here would be inconsistent with existing convention rather than fixing a real gap.

All of the above verified via nox -s lint, nox -s format -- --check, nox -s typecheck, nox -s dead_code, and a targeted nox -s unit_tests/coverage_report run scoped to features/credential_injection.feature (121 scenarios, 0 failed; the new/changed lines in application.py are now covered).

Re-requesting review.

Thanks for the review @hurui200320 — addressed in the amended commit (force-pushed, same branch): **Major** - Test tautology: fixed. The positive scenario now asserts `app.agent_factory.credentials["openai_compatible"]` actually matches the injected dict (not just that a mocked chat model responded). Added a negative scenario (no `credentials`, real/unmocked `build_chat_model`) confirming standalone mode still rejects `openai_compatible` with `Unsupported provider: ...` — unchanged behavior, verified rather than assumed. **Minor** - Interactive-session coverage: added, mirroring the single-shot scenario (mocks `input`/`print`, feeds one prompt then `exit`). - Docs: added a `credentials` example to README's Quick start and a cross-reference in `docs/guides/reasoning-aware-llm-agents.md`. - Step-file naming: checked against the repo's own convention — `credential_injection.feature` already splits steps across 15+ subsystem-named files (`credential_executor_steps.py`, `credential_factory_steps.py`, `credential_llm_error_steps.py`, etc.). `credential_application_steps.py` follows that established pattern, so left as-is (matches your own caveat: "unless the project has an explicit convention to split by subsystem"). - Deep constructor validation: intentionally not added. Issue #123 explicitly asks this parameter to *mirror* `Executor`'s existing `credentials` handling, and `Executor.__init__` itself only does the shallow `isinstance(..., dict)` check (deep structural validation lives solely in `AgentFactory` via `validate_credentials_structure`, shared to avoid duplicating that logic). Adding deep validation only on this entry point would diverge from the mirrored design and duplicate validation the factory already performs. Also added a scenario for the constructor's own non-dict-credentials rejection, since coverage showed that branch wasn't actually exercised. **Nits** - Docstring `Attributes` list: added `credentials`. - `tempfile.mkdtemp()` cleanup: left as-is — every other step file creating scenario temp dirs in this repo (dozens of them) follows the same no-cleanup pattern, so adding it only here would be inconsistent with existing convention rather than fixing a real gap. All of the above verified via `nox -s lint`, `nox -s format -- --check`, `nox -s typecheck`, `nox -s dead_code`, and a targeted `nox -s unit_tests`/`coverage_report` run scoped to `features/credential_injection.feature` (121 scenarios, 0 failed; the new/changed lines in `application.py` are now covered). Re-requesting review.

CoreRasurae requested review from hurui200320 2026-08-10 08:28:34 +00:00

hurui200320 approved these changes 2026-08-10 08:44:12 +00:00

hurui200320 left a comment

Copy link

PR Review: !128 (Ticket #123)

Verdict: Approve

The implementation correctly adds optional credentials injection to ReactiveCleverAgentsApp, forwarding it to the internal AgentFactory so that non-native providers (e.g. openai_compatible) work through the README "Quick start" entry point. All concerns from the previous review pass have been addressed: the positive Behave scenario now asserts that credentials actually reach AgentFactory.credentials, a negative scenario verifies unchanged standalone-mode rejection, an interactive-session scenario covers start_interactive_session(), and the README/guide docs are updated. The change is minimal, type-safe, and consistent with the existing Executor/AgentFactory credential-injection design (ADR-2026).

Critical Issues

None

Major Issues

None

Minor Issues

None

Nits

None

Summary

• src/cleveractors/core/application.py: the new credentials parameter is validated, stored, and threaded into AgentFactory(...) exactly where expected. No existing behavior changes when credentials is omitted.
• features/credential_injection.feature + features/steps/credential_application_steps.py: four new scenarios cover the happy path, credential forwarding, unchanged no-credentials rejection, interactive-session usage, and constructor input validation. The assertions are no longer tautological.
• README.md and docs/guides/reasoning-aware-llm-agents.md accurately document the new constructor option.
• CHANGELOG.md entry is accurate and appropriately scoped.

I reviewed the author’s response to the prior review and agree with the rationale for the items left as-is (step-file naming and temp-directory cleanup follow the project’s established subsystem-based conventions; deep credential-structure validation is intentionally delegated to AgentFactory/validate_credentials_structure, matching Executor). No blocking issues remain. Approved.

## PR Review: !128 (Ticket #123) ### Verdict: Approve The implementation correctly adds optional `credentials` injection to `ReactiveCleverAgentsApp`, forwarding it to the internal `AgentFactory` so that non-native providers (e.g. `openai_compatible`) work through the README "Quick start" entry point. All concerns from the previous review pass have been addressed: the positive Behave scenario now asserts that credentials actually reach `AgentFactory.credentials`, a negative scenario verifies unchanged standalone-mode rejection, an interactive-session scenario covers `start_interactive_session()`, and the README/guide docs are updated. The change is minimal, type-safe, and consistent with the existing `Executor`/`AgentFactory` credential-injection design (ADR-2026). ### Critical Issues None ### Major Issues None ### Minor Issues None ### Nits None ### Summary - `src/cleveractors/core/application.py`: the new `credentials` parameter is validated, stored, and threaded into `AgentFactory(...)` exactly where expected. No existing behavior changes when `credentials` is omitted. - `features/credential_injection.feature` + `features/steps/credential_application_steps.py`: four new scenarios cover the happy path, credential forwarding, unchanged no-credentials rejection, interactive-session usage, and constructor input validation. The assertions are no longer tautological. - `README.md` and `docs/guides/reasoning-aware-llm-agents.md` accurately document the new constructor option. - `CHANGELOG.md` entry is accurate and appropriately scoped. I reviewed the author’s response to the prior review and agree with the rationale for the items left as-is (step-file naming and temp-directory cleanup follow the project’s established subsystem-based conventions; deep credential-structure validation is intentionally delegated to `AgentFactory`/`validate_credentials_structure`, matching `Executor`). No blocking issues remain. Approved.

CoreRasurae added 1 commit 2026-08-10 10:33:18 +00:00

feat(application): support credential injection in ReactiveCleverAgentsApp ... bd07b39573

Add an optional `credentials: dict[str, dict[str, str]] | None` parameter
to `ReactiveCleverAgentsApp.__init__`, validated (must be a dict or None)
and forwarded verbatim to the internal `AgentFactory(...)` constructed by
`load_configuration()`.

Previously `ReactiveCleverAgentsApp` had no way to supply an `api_key`/
`base_url` for a non-native provider (anything outside `openai`/
`anthropic`/`google`, Actor Configuration Standard §4.4.1, e.g.
`openai_compatible`), so any agent using one failed with
`ConfigurationError: Unsupported provider: ...` as soon as it was invoked
via `run_single_shot()`/`start_interactive_session()`. `create_executor`/
`Executor` already supported this (ADR-2026 per-request credential
injection) but lacked this class's agent-template resolution and config
validation, forcing a choice between the two entry points' feature sets.
Threading `credentials` through closes that gap: a single code path now
supports template resolution, validation, and non-native-provider
credential injection together. Omitting `credentials` (the default)
leaves standalone/CLI-mode behavior unchanged.

BDD coverage (`features/credential_injection.feature`,
`features/steps/credential_application_steps.py`) now includes:
- a positive scenario asserting the injected `openai_compatible`
  credentials actually reach `AgentFactory.credentials`, not just that a
  mocked chat model was invoked;
- a negative scenario (no credentials, unmocked provider resolution)
  confirming standalone-mode behavior is unchanged: the agent still
  reports `Unsupported provider: openai_compatible`;
- an interactive-session scenario, mirroring the single-shot one, so both
  entry points named in the issue's acceptance criteria are exercised;
- a constructor-validation scenario for a non-dict `credentials` value.

Also updates the class docstring's Attributes list, and cross-references
the new constructor option from README.md's Quick start and
docs/guides/reasoning-aware-llm-agents.md.

ISSUES CLOSED: #123

CoreRasurae force-pushed feature/application-credential-injection from 9101063cbd to bd07b39573 2026-08-10 10:33:18 +00:00 Compare

CoreRasurae merged commit bd07b39573 into master 2026-08-10 10:48:32 +00:00

CoreRasurae deleted branch feature/application-credential-injection 2026-08-10 10:48:42 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

hurui200320

Labels

Clear labels

  

auto/blocked-by-deps

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.

  

auto/ci-timeout

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.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

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.

  

auto/last-attempt-tier-min

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.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

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.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

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.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

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.

  

Needs Feedback

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

  

Signed-off: Owner

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.

  

Signed-off: Scrum Master

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.

  

Signed-off: Tech Lead

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.

  

Spike

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 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

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

v2.1.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#123 ReactiveCleverAgentsApp has no credentials param, so non-native providers (openai_compatible) can never work through it

cleveragents/cleveractors-core

Reference

cleveragents/cleveractors-core!128

No description provided.