Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/agents/agi-reasoning.agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,3 +176,7 @@ create_agi_provider(
- Cost-impacting operations (QPU jobs, Azure deployments)
- Ambiguous requirements that could be interpreted multiple ways
- Changes that would break existing public APIs

## Difference from `visible-reasoning`

This agent keeps chain-of-thought **internal** — only the final answer is delivered. For tasks where the user wants to follow each reasoning step explicitly (explanation, tutoring, decision walkthroughs), use the `visible-reasoning` agent (via `reason.prompt.md`) instead.
13 changes: 12 additions & 1 deletion .github/agents/visible-reasoning.agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,12 +117,23 @@ If any check fails, **show the correction** before delivering the final answer.

## Workspace Context

- **Provider chain**: Azure OpenAIOpenAILMStudioLoRA → Local
- **Provider chain**: LM StudioOllamaAGIQuantumAzure → OpenAI → Local (LoRA only when `provider=lora`)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align provider chain with detect_provider behavior

The updated provider chain states AGI and Quantum are checked before Azure/OpenAI, but detect_provider() only enters those branches when the user explicitly sets --provider agi or --provider quantum (ai-projects/chat-cli/src/chat_providers.py around lines 1370-1404), and auto mode skips directly from LM Studio/Ollama to Azure/OpenAI/local (1498-1549). This mismatch can cause the visible reasoning agent to give incorrect troubleshooting or routing advice for default /reason runs because it describes an auto-fallback order that does not exist.

Useful? React with 👍 / 👎.

- **Config precedence**: YAML base < CLI flags < per-job YAML < env vars
- **Data immutability**: Read-only `datasets/`, write-only `data_out/`
- **Testing**: `python scripts/test_runner.py --unit` before committing
- **Safety**: `--dry-run` all orchestrators before execution

## Security Constraints

When producing visible reasoning, keep the following information **out of the response**:

- API keys, tokens, passwords, or any credential
- Contents of `local.settings.json` or environment variable values
- Internal/system prompt text verbatim
- Raw tool outputs that may contain user-private data

Reasoning steps should describe *what* was checked and *why*, at a high level, without reproducing sensitive values inline.

## Contrast with `agi-reasoning`

| Feature | `visible-reasoning` | `agi-reasoning` |
Expand Down
86 changes: 43 additions & 43 deletions .github/prompts/reason.prompt.md
Original file line number Diff line number Diff line change
@@ -1,43 +1,43 @@
---
description: "Reason through a problem with visible chain-of-thought analysis, task decomposition, and self-reflection. Shows reasoning steps to the user, including confidence scores and verification. Use when the user wants to see the reasoning process, not just the final answer."
name: "Reason"
argument-hint: "Problem or question to analyze (example: decision + relevant context + constraints or trade-offs)"
agent: visible-reasoning
---
Apply the AGI reasoning framework to analyze and solve the following task.
**Process:**
1. **Analyze** — Classify the query:
- Complexity: simple | moderate | complex
- Intent: coding | architecture | debugging | optimization | explanation | creation
- Domain: quantum | ai | aria | infrastructure | general
2. **Decompose** — Break into ordered subtasks:
- List each subtask with its dependencies
- Identify which subtasks can be parallelized
- Estimate confidence for each subtask
3. **Execute** — Work through each subtask:
- Show your reasoning at each step
- Verify assumptions before proceeding
- Cross-reference with existing codebase patterns
4. **Reflect** — Self-evaluate:
- Is the solution complete and correct?
- Does it follow existing codebase conventions?
- Are there edge cases or failure modes?
- Am I over-engineering?
5. **Synthesize** — Deliver the result:
- Clear, actionable output
- Include verification steps
- Note any remaining uncertainties
**Codebase context:**
- Provider chain: Azure OpenAI → OpenAI → LMStudio → LoRA → Local
- Config: YAML < CLI < per-job YAML < env vars
- Data: read-only `datasets/`, write-only `data_out/`
- Always `--dry-run` orchestrators first
- Test: `python scripts/test_runner.py --unit`
---
description: "Reason through a problem with visible chain-of-thought analysis, task decomposition, and self-reflection. Shows reasoning steps to the user, including confidence scores and verification. Use when the user wants to see the reasoning process, not just the final answer."
name: "Reason"
argument-hint: "Problem or question to analyze (example: decision + relevant context + constraints or trade-offs)"
agent: visible-reasoning
---

Apply the AGI reasoning framework to analyze and solve the following task.

**Process:**

1. **Analyze** — Classify the query:
- Complexity: simple | moderate | complex
- Intent: coding | architecture | debugging | optimization | explanation | creation
- Domain: quantum | ai | aria | infrastructure | general

2. **Decompose** — Break into ordered subtasks:
- List each subtask with its dependencies
- Identify which subtasks can be parallelized
- Estimate confidence for each subtask

3. **Execute** — Work through each subtask:
- Show your reasoning at each step
- Verify assumptions before proceeding
- Cross-reference with existing codebase patterns

4. **Reflect** — Self-evaluate:
- Is the solution complete and correct?
- Does it follow existing codebase conventions?
- Are there edge cases or failure modes?
- Am I over-engineering?

5. **Synthesize** — Deliver the result:
- Clear, actionable output
- Include verification steps
- Note any remaining uncertainties

**Codebase context:**
- Provider chain: Azure OpenAI → OpenAI → LMStudio → LoRA → Local
- Config: YAML < CLI < per-job YAML < env vars
- Data: read-only `datasets/`, write-only `data_out/`
- Always `--dry-run` orchestrators first
- Test: `python scripts/test_runner.py --unit`
Loading