CleverAgents should support Claude's batch processing #1251

Open
opened 2026-04-01 22:04:30 +00:00 by brent.edwards · 3 comments
Member

One way to lower the cost of LLMs is to use batch processing. Claude supports the Batch Processing mode, which is half the usual cost, at the cost of taking an hour or longer to respond.

This epic represents all stages of adding batch processing. It includes, but is not limited to:

  1. Representing when an action uses batch processing
  2. Handling the long wait for a response.
  3. All testing that uses batch processing.
One way to lower the cost of LLMs is to use batch processing. Claude supports the [Batch Processing](https://platform.claude.com/docs/en/build-with-claude/batch-processing) mode, which is half the usual cost, at the cost of taking an hour or longer to respond. This epic represents all stages of adding batch processing. It includes, but is not limited to: 1. Representing when an action uses batch processing 2. Handling the long wait for a response. 3. All testing that uses batch processing.
freemo added this to the v3.8.0 milestone 2026-04-02 08:08:54 +00:00
Owner

🤖 Backlog Groomer — Epic Completeness Check

This epic (Type/Epic) appears to have zero child issues linked to it. An epic with no children cannot be tracked or implemented.

Epic scope from description:

  1. Representing when an action uses batch processing
  2. Handling the long wait for a response
  3. All testing that uses batch processing

Recommended actions:

  • Decompose this epic into concrete child issues covering each of the above areas
  • Link child issues to this epic using Forgejo's dependency system (child issues should block this epic)
  • Consider whether this epic should be in State/Unverified or moved to State/Verified once decomposed

This epic is currently in State/Unverified which is appropriate until it is decomposed and verified.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

🤖 **Backlog Groomer — Epic Completeness Check** This epic (`Type/Epic`) appears to have **zero child issues** linked to it. An epic with no children cannot be tracked or implemented. **Epic scope from description:** 1. Representing when an action uses batch processing 2. Handling the long wait for a response 3. All testing that uses batch processing **Recommended actions:** - Decompose this epic into concrete child issues covering each of the above areas - Link child issues to this epic using Forgejo's dependency system (child issues should block this epic) - Consider whether this epic should be in `State/Unverified` or moved to `State/Verified` once decomposed This epic is currently in `State/Unverified` which is appropriate until it is decomposed and verified. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
freemo self-assigned this 2026-04-02 18:45:27 +00:00
Owner

Hierarchical Compliance Fix: This Epic was detected as an orphan (no parent Legendary).

Solution: Linked to Legendary #378 (Post-MVP Deferred Work) based on strategic alignment — Claude batch processing is a post-MVP server/LLM backend feature that fits within the Post-MVP Deferred Work strategic pillar.

Complete Hierarchy: Issues → Epic #1251 → Legendary #378 (Post-MVP Deferred Work)

Note: This Epic also needs child issues decomposed before implementation can begin. The Epic body describes the scope but has no formal child issues linked yet.


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

**Hierarchical Compliance Fix**: This Epic was detected as an orphan (no parent Legendary). **Solution**: Linked to Legendary #378 (Post-MVP Deferred Work) based on strategic alignment — Claude batch processing is a post-MVP server/LLM backend feature that fits within the Post-MVP Deferred Work strategic pillar. **Complete Hierarchy**: Issues → Epic #1251 → Legendary #378 (Post-MVP Deferred Work) **Note**: This Epic also needs child issues decomposed before implementation can begin. The Epic body describes the scope but has no formal child issues linked yet. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Owner

Epic Planning Complete — Child Issues Created

This Epic has been decomposed into 3 atomic child issues with proper dependency chain:

Child Issues

  • #4928feat(actors): add BatchProcessingMode to ActorConfiguration for Claude batch API support (start here — no blockers)
  • #4929feat(providers): implement ClaudeBatchProvider for async batch request submission and polling (blocked by #4928)
  • #4930feat(actors): wire batch processing dispatch into ActorExecutor — route batch-mode actors to ClaudeBatchProvider (blocked by #4928, #4929)

Dependency Chain

#4928 (ActorConfiguration.batch_processing field)
  ↓ blocks
#4929 (ClaudeBatchProvider implementation)
  ↓ blocks
#4930 (ActorExecutor dispatch wiring)
  ↓ all block
#1251 (This Epic)
  ↓ blocks
#378 (Legendary: Post-MVP Deferred Work)

Hierarchy

Issues → Epic #1251 → Legendary #378 (Post-MVP Deferred Work)


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Epic Planning Complete — Child Issues Created This Epic has been decomposed into 3 atomic child issues with proper dependency chain: ### Child Issues - [ ] #4928 — `feat(actors): add BatchProcessingMode to ActorConfiguration for Claude batch API support` *(start here — no blockers)* - [ ] #4929 — `feat(providers): implement ClaudeBatchProvider for async batch request submission and polling` *(blocked by #4928)* - [ ] #4930 — `feat(actors): wire batch processing dispatch into ActorExecutor — route batch-mode actors to ClaudeBatchProvider` *(blocked by #4928, #4929)* ### Dependency Chain ``` #4928 (ActorConfiguration.batch_processing field) ↓ blocks #4929 (ClaudeBatchProvider implementation) ↓ blocks #4930 (ActorExecutor dispatch wiring) ↓ all block #1251 (This Epic) ↓ blocks #378 (Legendary: Post-MVP Deferred Work) ``` ### Hierarchy Issues → Epic #1251 → Legendary #378 (Post-MVP Deferred Work) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#1251
No description provided.