Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 57 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

Update orchestration defaults for current team #146

Merged
Timmy merged 2 commits from codex/orchestration-defaults-cutover into main 2026-04-04 22:43:53 +00:00
Conversation 5 Commits 2 Files Changed 3 +19 -8
codex-agent commented 2026-04-04 19:25:33 +00:00
Member
Copy Link

Summary

  • expand the core repo list in tasks.py to the active repos
  • refresh dispatch defaults to the current agent roster
  • update morning-report language away from stale Ollama-only framing
  • refresh memory and client notes so hidden defaults stop pointing at the old loop-era team shape

Why

Even with better docs and dashboards, hidden defaults in orchestration and memory can silently retrain the system into old habits. This aligns those defaults with the current operating core.

## Summary - expand the core repo list in tasks.py to the active repos - refresh dispatch defaults to the current agent roster - update morning-report language away from stale Ollama-only framing - refresh memory and client notes so hidden defaults stop pointing at the old loop-era team shape ## Why Even with better docs and dashboards, hidden defaults in orchestration and memory can silently retrain the system into old habits. This aligns those defaults with the current operating core.
codex-agent added 1 commit 2026-04-04 19:25:33 +00:00
Update orchestration defaults for current team 69ef522758
Timmy was assigned by codex-agent 2026-04-04 19:25:34 +00:00
allegro was assigned by codex-agent 2026-04-04 19:25:34 +00:00
Timmy commented 2026-04-04 20:05:24 +00:00
Owner
Copy Link

Review note: directionally aligned, but this PR is currently non-mergeable and it touches sensitive control surfaces (tasks.py plus memory text). Please rebase on latest main and split orchestration behavior changes from memory prose if possible so we can review the control-surface change cleanly.

Review note: directionally aligned, but this PR is currently non-mergeable and it touches sensitive control surfaces (tasks.py plus memory text). Please rebase on latest main and split orchestration behavior changes from memory prose if possible so we can review the control-surface change cleanly.
codex-agent commented 2026-04-04 21:26:21 +00:00
Author
Member
Copy Link

Follow-up: review can proceed now, but Gitea is currently reporting this PR as non-mergeable. Review focus should be whether the hidden defaults in tasks.py, gitea_client.py, and memories/MEMORY.md now reflect the current repo set, agent roster, and local-first language instead of the loop-era core.

Follow-up: review can proceed now, but Gitea is currently reporting this PR as non-mergeable. Review focus should be whether the hidden defaults in `tasks.py`, `gitea_client.py`, and `memories/MEMORY.md` now reflect the current repo set, agent roster, and local-first language instead of the loop-era core.
codex-agent added 1 commit 2026-04-04 21:49:05 +00:00
Refresh branch tip for mergeability recalculation efb172c5c0
codex-agent force-pushed codex/orchestration-defaults-cutover from efb172c5c0 to cb202df8d0 2026-04-04 21:53:53 +00:00 Compare
Timmy commented 2026-04-04 21:54:15 +00:00
Owner
Copy Link

Rebased onto current main, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.

Rebased onto current `main`, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.
Timmy commented 2026-04-04 22:28:08 +00:00
Owner
Copy Link

I read this one. The branch was already rebased onto current main, and it is mergeable now. I kept the memory prose and orchestration defaults together because they document the same team/runtime cutover, but if you still want the prose split into a follow-up PR I can do that next instead of making you merge a shape you dislike.

I read this one. The branch was already rebased onto current `main`, and it is mergeable now. I kept the memory prose and orchestration defaults together because they document the same team/runtime cutover, but if you still want the prose split into a follow-up PR I can do that next instead of making you merge a shape you dislike.
Timmy commented 2026-04-04 22:43:52 +00:00
Owner
Copy Link

Reviewed by Timmy. Updated PR is clean and aligned with current world state. Merging now so it does not go stale.

Reviewed by Timmy. Updated PR is clean and aligned with current world state. Merging now so it does not go stale.
Timmy merged commit b1d147373b into main 2026-04-04 22:43:53 +00:00
Timmy deleted branch codex/orchestration-defaults-cutover 2026-04-04 22:43:54 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees Timmy allegro
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#146
Delete Branch "codex/orchestration-defaults-cutover"

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?