Skip to content

Expose llm_call tool and refresh docs - #3

Merged
zby merged 1 commit into
mainfrom
codex/update-tool-name-to-llm_call
Nov 20, 2025
Merged

zby merged 1 commit into
mainfrom
codex/update-tool-name-to-llm_call

Conversation

@zby

@zby zby commented Nov 20, 2025

Copy link
Copy Markdown
Owner

Summary

  • expose a public llm_call tool that wraps TemplateCall with LLM-facing parameters
  • refresh templatecall documentation and README to clarify programmer vs LLM perspectives and the new tool name
  • update sample orchestrator templates to use llm_call in prompts and instructions

Testing

  • not run (not requested)

Codex Task

@zby
zby merged commit 3e1c114 into main Nov 20, 2025
2 checks passed
zby added a commit that referenced this pull request Nov 20, 2025
Added important concepts from README and templatecall docs, plus
sophisticated tool approval system to replace special-cased worker
creation approval.

Key additions:

1. Context Bloat Problem section
   - Explains how bloated prompts drift and fail unpredictably
   - Solution: decompose into focused sub-calls with tight scope

2. Enhanced Recursive Call Problem
   - Added benefits: composability, uniformity, programmer ergonomics
   - Clarified this is specific to llm library, not all frameworks
   - Changed framing: "looking for a framework" vs. "better architecture"

3. Concrete benefits under Worker Delegation
   - Tight context per call (single unit of work)
   - Guardrails by construction (enforced in code, not instructions)
   - Reproducibility (explicit, loggable, auditable)
   - Iteration speed (workers evolve independently)

4. New Tool Call Approval System (Key Capability #3)
   - Pre-approved tools: benign operations execute automatically
   - Human-in-the-loop: consequential actions require approval
   - Configurable policies with sensible defaults
   - User sees full context, can approve/reject/modify

5. Worker creation now general case
   - Capability #4: subject to tool approval policy (no special case)
   - Design principle updated: sophisticated approval controls
   - Summary emphasizes approval system, worker creation as instance

The spec now clearly states we're looking for a framework that either
provides these capabilities or can be extended to support them.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
zby added a commit that referenced this pull request Jan 27, 2026
- Remove completed/outdated review notes:
  - simplify-runtime-{contracts,deps,shared}.md
  - useless-features-audit.md and 2026-01-13 follow-up
  - sloc-reduction-patterns.md (completed refactoring)

- Update file paths for recent refactoring:
  - runtime/shared.py → runtime/runtime.py
  - runtime/deps.py → runtime/context.py
  - WorkerRuntime → CallContext

- Update toolset-instantiation-questions.md: mark question #3 resolved
- Update dynamic-workers-runtime-design.md: fix task reference path
- Add update note to review-solid.md documenting path changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant