mirror of
https://github.com/mikeyobrien/ralph-orchestrator.git
synced 2026-04-25 07:05:57 +03:00
[GH-ISSUE #40] Ralph is open adapters not configured in ralph.yml #10
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ralph-orchestrator#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nietzscheson on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/40
Hey guys!
I'm configuring Ralph just with Gemini-CLI
agent: gemini
agent_priority:
prompt_file: PROMPT.md
max_iterations: 100
max_runtime: 14400
verbose: false
adapters:
gemini:
enabled: true
timeout: 300
acp:
enabled: true
timeout: 300
tool_permissions:
agent_command: gemini
agent_args: []
permission_mode: auto_approve
permission_allowlist: ["fs/", "terminal/"]
And when I run ralph -c ralph.yml, I got:
Error output: Check stderr output for details
2026-01-08 22:52:40,210 - ralph-orchestrator - INFO - Falling back to kiro
2026-01-08 22:52:40,210 - ralph.adapter.kiro - INFO - Executing Kiro chat async - Prompt file: PROMPT.md, Timeout: 600s
2026-01-08 22:52:40,210 - ralph.adapter.kiro - INFO - Executing Kiro chat async - Prompt file: PROMPT.md, Timeout: 600s
^C2026-01-08 22:52:52,209 - ralph-orchestrator - INFO - Received signal 2, initiating graceful shutdown...
2026-01-08 22:52:52,212 - ralph.adapter.kiro - WARNING - Async Kiro chat failed - Return code: -2
2026-01-08 22:52:52,212 - ralph.adapter.kiro - WARNING - Async Kiro chat failed - Return code: -2
Ralph is trying to open adapters not configured in the config:
2026-01-08 22:41:31,752 - ralph.adapter.kiro - INFO - Kiro adapter initialized - Command: kiro-cli, Default timeout: 600s, Trust tools: True
2026-01-08 22:41:31,755 - ralph.adapter.qchat - INFO - Q Chat adapter initialized - Command: q, Default timeout: 600s, Trust tools: True
2026-01-08 22:41:40,455 - ralph.adapter.kiro - INFO - Executing Kiro chat async - Prompt file: PROMPT.md, Timeout: 600s
2026-01-08 22:42:06,458 - ralph.adapter.kiro - WARNING - Async Kiro chat failed - Return code: -2
2026-01-08 22:42:18,174 - ralph.adapter.kiro - INFO - Kiro adapter initialized - Command: kiro-cli, Default timeout: 600s, Trust tools: True
2026-01-08 22:42:18,176 - ralph.adapter.qchat - INFO - Q Chat adapter initialized - Command: q, Default timeout: 600s, Trust tools: True
2026-01-08 22:42:27,678 - ralph.adapter.kiro - INFO - Executing Kiro chat async - Prompt file: PROMPT.md, Timeout: 600s
2026-01-08 22:52:27,676 - ralph.adapter.kiro - WARNING - Async Kiro chat timed out after 600 seconds
2026-01-08 22:52:40,210 - ralph.adapter.kiro - INFO - Executing Kiro chat async - Prompt file: PROMPT.md, Timeout: 600s
2026-01-08 22:52:52,212 - ralph.adapter.kiro - WARNING - Async Kiro chat failed - Return code: -2
@mikeyobrien commented on GitHub (Jan 9, 2026):
Looks like a regression when the kiro migration was merged. Could you try explicitly disabling kiro in the yml?