You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Determining the Minimum Supported Pydantic Version (Binary Cut)
This note documents how we determined the lowest Pydantic 2.x version that
works across our supported Python versions (3.10–3.14) using uv and pytest.
It also records the final requirement change made to pyproject.toml.
Objective
Identify the minimum Pydantic version that passes our test suite across
Python 3.10, 3.11, 3.12, 3.13, and 3.14.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GitHub Issue: Enable Schema-Formatted Output for Tool-Using Chains
1. Problem:
Currently, the llm CLI's --schema option applies to the direct output of a single Language Model (LLM) call. When tools (via --tool or --functions) are used, the LLM engages in a multi-step chain (e.g., ReAct pattern) where intermediate outputs are tool call requests or textual reasoning. There's no direct way to specify that the final, user-visible result of such a multi-step, tool-using chain should conform to a user-defined schema. The existing --schema option doesn't automatically apply to the culmination of this chain.
2. Alternatives Considered:
A. New CLI Option: Introducing a distinct option (e.g., --final-schema or --output-schema) specifically for specifying the schema of the final output after a tool chain. This would keep the existing --schema behavior for direct, single-turn schema output and make the post-chain formatting explicit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bottom-line: NIH’s new Public Access Policy (NOT-OD-25-047) scraps the 12-month waiting period and makes every NIH-funded paper publicly available immediately at publication, starting with manuscripts accepted on or after December 31 2025.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large language model (LLM) coding assistants like Sourcegraph Cody, Aider, and Tabby help developers generate and apply code changes. This report examines how these open-source tools prompt LLMs to produce patches, integrate the changes into code, handle common issues, verify results, and what challenges remain.
Prompting Strategies
Structured Prompts for Code Edits – These assistants carefully craft prompts so the LLM knows exactly how to output changes. For example, Aider uses specialized edit formats: it can ask the LLM for a full file rewrite or a diff. Aider often defaults to a diff format, where the LLM is told to return only the changed parts of files using a syntax similar to a unified diff or marked “search/replace” blocks. This reduces token usage and focuses the LLM on the edits. The prompt includes instructions like “produce changes in this format” with file paths and code fences, so the model returns patches instead
Configurable script for filtering files found in a git repo and copying content to clipboard
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters