sssss

[5hy7xz92nd-oss]

sssss@5hy7xz92nd-oss @claude @codex @grok
@openai @patpat @weareone10billion @Rabbitsync.
gh pr checkout 62 gh pr checkout 62

[Copilot]

Pull request overview

Adds new developer-facing utilities to improve observability and agent-style composition in LargeLanguageModels, alongside a significant documentation refresh (README + new docs files) and dependency lockfile updates.

Changes:

• Introduces two actor-based, in-memory logging/storing utilities for LLM request failures (LLMErrorLogger, FailedLLMResponseStore) plus LLMRequestHandling convenience wrappers.
• Adds a simple sequential Observer → Research → Decision agent pipeline abstraction (LLMAgentPipeline).
• Expands and reorganizes project documentation (README overhaul + new docs/ files, contributing guide, changelog, PR template).

Reviewed changes

Copilot reviewed 9 out of 10 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
Sources/LargeLanguageModels/Intramodular/LLMs/Logging/LLMErrorLogger.swift	Adds an actor-backed error logger and a complete(...loggingErrorsTo:) wrapper.
Sources/LargeLanguageModels/Intramodular/LLMs/Logging/FailedLLMResponseStore.swift	Adds an actor-backed store for failed chat prompts with JSONL export and a complete(...recordingFailuresIn:) wrapper.
Sources/LargeLanguageModels/Intramodular/LLMs/Agents/LLMAgentPipeline.swift	Introduces a basic multi-stage agent pipeline and default stages.
README.md	Major doc restructure: architecture overview, dependency graph, roadmap revamp, and more.
Package.resolved	Updates dependency lock revisions/hashes.
docs/README.md	Adds a documentation index page.
docs/ARCHITECTURE.md	Adds architecture/layering documentation and a dependency graph.
CONTRIBUTING.md	Adds contributor setup/process guidance.
CHANGELOG.md	Introduces changelog with initial [Unreleased] notes.
.github/PULL_REQUEST_TEMPLATE.md	Adds a PR template/checklist aligned with docs + layering expectations.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[5hy7xz92nd-oss]

@5hy7xz92nd-oss @copilot @copilot @Rabbitsync @WEAREONE10BILLION @manus @MANUSWEAREONE10BILLION @patpat @grok @openai @agent @agent Coordinator

[5hy7xz92nd-oss]

@5hy7xz92nd-oss @copilot @copilot

[Copilot]

Pull request overview

Copilot reviewed 9 out of 10 changed files in this pull request and generated no new comments.

Suppressed comments (6)

Sources/LargeLanguageModels/Intramodular/LLMs/Logging/FailedLLMResponseStore.swift:75

• exportAsJSONL() is new behavior that’s easy to regress (date encoding, line separation, JSON validity per line). There are existing unit tests under Tests/LargeLanguageModels; consider adding a focused test that records a couple of entries and asserts each line decodes back into FailedChatResponse.

    public func exportAsJSONL() throws -> String {
        let encoder = JSONEncoder()
        encoder.outputFormatting = []
        encoder.dateEncodingStrategy = .iso8601
        return try _entries
            .map { try String(decoding: encoder.encode($0), as: UTF8.self) }
            .joined(separator: "\n")
    }

README.md:2

• The GitHub admonition syntax requires the marker to start immediately after > (e.g. > [!IMPORTANT]). With the emoji prefix (> 🕴️[!IMPORTANT]), the admonition likely won’t render as an IMPORTANT callout.

> 🕴️[!IMPORTANT]
> This package is presently in its alpha stage of development (2026-03-04).

Sources/LargeLanguageModels/Intramodular/LLMs/Logging/LLMErrorLogger.swift:80

• The doc comment says loggingErrorsTo defaults to LLMErrorLogger.shared, but the method signature requires the argument. This is a doc/API mismatch and makes the convenience API harder to use.

    public func complete<Prompt: AbstractLLM.Prompt>(
        _ prompt: Prompt,
        parameters: Prompt.CompletionParameters,
        loggingErrorsTo logger: LLMErrorLogger
    ) async throws -> Prompt.Completion {

Sources/LargeLanguageModels/Intramodular/LLMs/Logging/LLMErrorLogger.swift:55

• LLMErrorLogger stores entries indefinitely in an in-memory singleton. In long-running processes this can grow without bound, and promptDescription may include sensitive prompt content depending on Prompt’s CustomStringConvertible/CustomDebugStringConvertible behavior. Consider adding a retention policy (e.g. max entry count / ring buffer) and/or a redaction strategy for prompt details.

    /// Append a new entry to the log.
    public func log(_ entry: AbstractLLM.ErrorLogEntry) {
        _entries.append(entry)
    }

Sources/LargeLanguageModels/Intramodular/LLMs/Logging/FailedLLMResponseStore.swift:56

• FailedLLMResponseStore retains full chat prompts (prompt.messages) indefinitely in an in-memory singleton, and exportAsJSONL() will serialize that content. This can unintentionally persist secrets/PII and can grow memory usage without bound. Consider adding opt-in/redaction (e.g. strip user content, hash, or truncate) and a retention policy (max entries).

    /// Append a new failed-response record.
    public func record(_ entry: AbstractLLM.FailedChatResponse) {
        _entries.append(entry)
    }

Sources/LargeLanguageModels/Intramodular/LLMs/Agents/LLMAgentPipeline.swift:145

• The new agent pipeline wiring (Observer → Research → Decision) has no unit coverage. Since LLMAgentStage.process and AgentPipeline.run are pure orchestration, consider adding a test with a lightweight LLMRequestHandling stub that returns deterministic completions, then assert stage chaining and outputs.

        public func run(input: String) async throws -> AgentPipelineResult {
            let observation = try await observer.process(input: input, using: llm)
            let research = try await researcher.process(input: observation, using: llm)
            let decision = try await decisionMaker.process(input: research, using: llm)
            return AgentPipelineResult(
                input: input,
                observation: observation,
                research: research,
                decision: decision
            )

[5hy7xz92nd-oss]

@5hy7xz92nd-oss @claude @codex @grok
@openai @patpat @weareone10billion @Rabbitsync

[5hy7xz92nd-oss]

@5hy7xz92nd-oss @claude @codex @grok
@openai @patpat @weareone10billion @Rabbitsync

[5hy7xz92nd-oss]

@5hy7xz92nd-oss @claude @codex @grok
@openai @patpat @weareone10billion @Rabbitsync execute

[5hy7xz92nd-oss]

Copilot pull request summaries
AI-generated summaries of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review. See Creating a pull request summary with GitHub Copilot.

Copilot in GitHub Desktop
Automatically generate commit messages and descriptions with Copilot in GitHub Desktop based on the changes you make to your project.

Agentic features
These features can work autonomously without direct human supervision. However, they typically need human approval to perform sensitive actions, such as running commands in a developer's terminal or merging a pull request.

Copilot CLI
A command line interface that lets you use Copilot in your terminal. Use the CLI to add features or fix bugs, then create a pull request. Start Copilot working on a task in your terminal, then continue working in the same session on GitHub.com, or on your mobile. See About GitHub Copilot CLI.

GitHub Copilot app
A desktop application for agent-driven development. From the app, you can run multiple agent sessions in parallel across your repositories, manage issues and pull requests, and set up automations to run tasks on a schedule. See About the GitHub Copilot app.

Copilot cloud agent
An autonomous AI agent that can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and create a pull request when you're ready. You can also assign a GitHub issue to Copilot or ask it to open a pull request directly to complete a task. See GitHub Copilot cloud agent.

Third-party coding agents (public preview)
You can use third-party coding agents alongside Copilot cloud agent. Third-party agents are subject to the same security protections, mitigations, and limitations as Copilot cloud agent. See About third-party coding agents.

Copilot code review
AI-generated code review suggestions to help you write better code. See Using GitHub Copilot code review.

Several tools in Copilot code review are in public preview and subject to change. See About GitHub Copilot code review.

Agent mode in IDEs
Allow Copilot to work autonomously in the IDE. Copilot will determine which files to make changes to, offer code changes and terminal commands for the user's approval, and iterate to remediate issues until the original task is complete.

Features for customization
These features can be used to add context to Copilot and improve its performance. For a comparison of when to use each feature, see Copilot customization cheat sheet.

Copilot Spaces
Organize and centralize relevant content—like code, docs, specs, and more—into Spaces that ground Copilot’s responses in the right context for a specific task. See About GitHub Copilot Spaces.

Custom instructions
Enhance responses by providing contextual details on your preferences, tools, and requirements. See About customizing GitHub Copilot responses.

Copilot Memory (public preview)
Copilot can deduce and store useful information about a repository, which Copilot cloud agent and Copilot code review can use to improve the quality of their output when working in that repository. For more information, see About GitHub Copilot Memory.

Prompt files
Build and share reusable prompt instructions with additional context. A prompt file is a Markdown file, stored in your workspace, that mimics the existing format of writing prompts. See About customizing GitHub Copilot responses.

MCP servers
You can configure Model Context Protocol (MCP) servers for many Copilot features, giving Copilot access to external tools or data sources. See About Model Context Protocol (MCP).

Agent skills
Create folders of instructions, scripts, and resources that Copilot can load when relevant to improve its performance in specialized tasks. See About agent skills.

Custom agents
Create specialized versions of Copilot cloud agent with access to specific tools, instructions, and MCP servers. See About custom agents.

Features for administrators
The following features are available to organization and enterprise owners with a Copilot Business or Copilot Enterprise plan.

Policy management
Manage policies for Copilot in your organization or enterprise. See Managing policies and features for GitHub Copilot in your organization and Managing policies and features for GitHub Copilot in your enterprise.

Access management
Enterprise owners can specify which organizations in the enterprise can use Copilot, and organization owners can specify which organization members can use Copilot. See Managing access to GitHub Copilot in your organization and Managing access to Copilot in your enterprise.

Usage data
Review Copilot usage data within your organization or enterprise to inform how to manage access and drive adoption of Copilot. See Reviewing user activity data for GitHub Copilot in your organization and Viewing Copilot license usage in your enterprise.

Audit logs
Review audit logs for Copilot in your enterprise to understand what actions have been taken and by which users. See Reviewing audit logs for GitHub Copilot.

File exclusions
Configure Copilot to ignore certain files. This can be useful if you have files that you don't want to be available to Copilot. See Excluding content from GitHub Copilot.

Next steps
To learn more about the plans available for GitHub Copilot, see Plans for GitHub Copilot.
To start using Copilot, see Setting up GitHub Copilot.

[5hy7xz92nd-oss]

Copilot pull request summaries
AI-generated summaries of the changes that were made in a pull request, which files they impact, and what a reviewer should focus on when they conduct their review. See Creating a pull request summary with GitHub Copilot.

Copilot in GitHub Desktop
Automatically generate commit messages and descriptions with Copilot in GitHub Desktop based on the changes you make to your project.

Agentic features
These features can work autonomously without direct human supervision. However, they typically need human approval to perform sensitive actions, such as running commands in a developer's terminal or merging a pull request.

Copilot CLI
A command line interface that lets you use Copilot in your terminal. Use the CLI to add features or fix bugs, then create a pull request. Start Copilot working on a task in your terminal, then continue working in the same session on GitHub.com, or on your mobile. See About GitHub Copilot CLI.

GitHub Copilot app
A desktop application for agent-driven development. From the app, you can run multiple agent sessions in parallel across your repositories, manage issues and pull requests, and set up automations to run tasks on a schedule. See About the GitHub Copilot app.

Copilot cloud agent
An autonomous AI agent that can research a repository, create an implementation plan, and make code changes on a branch. You can review the diff, iterate, and create a pull request when you're ready. You can also assign a GitHub issue to Copilot or ask it to open a pull request directly to complete a task. See GitHub Copilot cloud agent.

Third-party coding agents (public preview)
You can use third-party coding agents alongside Copilot cloud agent. Third-party agents are subject to the same security protections, mitigations, and limitations as Copilot cloud agent. See About third-party coding agents.

Copilot code review
AI-generated code review suggestions to help you write better code. See Using GitHub Copilot code review.

Several tools in Copilot code review are in public preview and subject to change. See About GitHub Copilot code review.

Agent mode in IDEs
Allow Copilot to work autonomously in the IDE. Copilot will determine which files to make changes to, offer code changes and terminal commands for the user's approval, and iterate to remediate issues until the original task is complete.

Features for customization
These features can be used to add context to Copilot and improve its performance. For a comparison of when to use each feature, see Copilot customization cheat sheet.

Copilot Spaces
Organize and centralize relevant content—like code, docs, specs, and more—into Spaces that ground Copilot’s responses in the right context for a specific task. See About GitHub Copilot Spaces.

Custom instructions
Enhance responses by providing contextual details on your preferences, tools, and requirements. See About customizing GitHub Copilot responses.

Copilot Memory (public preview)
Copilot can deduce and store useful information about a repository, which Copilot cloud agent and Copilot code review can use to improve the quality of their output when working in that repository. For more information, see About GitHub Copilot Memory.

Prompt files
Build and share reusable prompt instructions with additional context. A prompt file is a Markdown file, stored in your workspace, that mimics the existing format of writing prompts. See About customizing GitHub Copilot responses.

MCP servers
You can configure Model Context Protocol (MCP) servers for many Copilot features, giving Copilot access to external tools or data sources. See About Model Context Protocol (MCP).

Agent skills
Create folders of instructions, scripts, and resources that Copilot can load when relevant to improve its performance in specialized tasks. See About agent skills.

Custom agents
Create specialized versions of Copilot cloud agent with access to specific tools, instructions, and MCP servers. See About custom agents.

Features for administrators
The following features are available to organization and enterprise owners with a Copilot Business or Copilot Enterprise plan.

Policy management
Manage policies for Copilot in your organization or enterprise. See Managing policies and features for GitHub Copilot in your organization and Managing policies and features for GitHub Copilot in your enterprise.

Access management
Enterprise owners can specify which organizations in the enterprise can use Copilot, and organization owners can specify which organization members can use Copilot. See Managing access to GitHub Copilot in your organization and Managing access to Copilot in your enterprise.

Usage data
Review Copilot usage data within your organization or enterprise to inform how to manage access and drive adoption of Copilot. See Reviewing user activity data for GitHub Copilot in your organization and Viewing Copilot license usage in your enterprise.

Audit logs
Review audit logs for Copilot in your enterprise to understand what actions have been taken and by which users. See Reviewing audit logs for GitHub Copilot.

File exclusions
Configure Copilot to ignore certain files. This can be useful if you have files that you don't want to be available to Copilot. See Excluding content from GitHub Copilot.

Next steps
To learn more about the plans available for GitHub Copilot, see Plans for GitHub Copilot.
To start using Copilot, see Setting up GitHub Copilot.

[Copilot]

Pull request overview

Copilot reviewed 117 out of 128 changed files in this pull request and generated 43 comments.

Suppressed comments (1)

Sources/AI/AnySpeechSynthesisRequestHandling.swift:38

• Equality compares only cached integer hash values. Distinct client objects can have colliding hashes and will then compare equal, violating identity semantics. Store and compare ObjectIdentifier itself, and use it for hashing.

    public static func == (lhs: AnySpeechSynthesisRequestHandling, rhs: AnySpeechSynthesisRequestHandling) -> Bool {
        lhs._hashValue == rhs._hashValue