Skip to content

fix: no "Start Task" when config specs dir - #33

Merged
notdp merged 2 commits into
notdp:mainfrom
yourtion:patch-1
Sep 20, 2025
Merged

fix: no "Start Task" when config specs dir#33
notdp merged 2 commits into
notdp:mainfrom
yourtion:patch-1

Conversation

@yourtion

@yourtion yourtion commented Sep 8, 2025

Copy link
Copy Markdown
Contributor

fix when change paths settings, the tasks.md no show the "Start Task"

fix when change paths settings, the `tasks.md` no show the "Start Task"
@notdp

notdp commented Sep 9, 2025

Copy link
Copy Markdown
Owner

Thank you for the PR, but there is a more serious bug in the settings feature now. I need more time to review it, thank you!

@yourtion

yourtion commented Sep 9, 2025

Copy link
Copy Markdown
Contributor Author

Yes, I'm trying to fix another settings bug about async file reading

@notdp

notdp commented Sep 10, 2025

Copy link
Copy Markdown
Owner

@yourtion

Thank you for your contribution! If you're interested, we could discuss more about best practices.

For instance, strategies for using Codex with or without plugins. Recently, I've noticed Claude Code Opus has been underperforming compared to before - it used to excel at solving complex bugs, but now only Codex seems capable of handling such tasks effectively.

One reason I've been updating plugins less frequently is that the reduction in model intelligence significantly impacts the specification workflow, often resulting in less clean code.

Fundamentally, for top-tier models like GPT-5 and Opus, computational resources directly translate to intelligence. When providers reallocate these resources, it affects all processes.

I recently experimented with Codex for problem-solving and found the results surprisingly good (while many Claude Code sessions just go in circles). However, due to Codex's less polished CLI and interaction experience, Claude Code remains the primary implementation tool.

I'm considering developing built-in commands or sub-agents to facilitate Claude Code's interaction with Codex. My other coding projects consume significant time - the upside is extensive practice in exploring best practices; the downside is less time for maintaining this project. I'm also considering using Claude Code Opus or Codex GPT-5 High to review some PRs.

Given all this, I'd suggest not spending too much time on minor issues unless they're actual usage bugs. Since I'm not a professional frontend developer, many parts of the code will need to be restructured and refactored. The overall architecture may undergo significant changes. For example, the settings feature - I envision a more user-friendly interface, as the current implementation is rather crude.

In summary, this repository aims to serve as a collection of AI usage best practices. Thank you again for your PR, and please feel free to share any ideas you have!

@notdp

notdp commented Sep 10, 2025

Copy link
Copy Markdown
Owner

Another interesting topic is the integration of git worktree. When using cc and codex simultaneously, effectively compare the output results and pick the better one!

@notdp
notdp merged commit de4f509 into notdp:main Sep 20, 2025
@notdp

notdp commented Sep 20, 2025

Copy link
Copy Markdown
Owner

Another interesting topic is the integration of git worktree. When using cc and codex simultaneously, effectively compare the output results and pick the better one!

@yourtion try this! https://github.com/notdp/worktree.sh

lanzhizhuxia pushed a commit to lanzhizhuxia/kiro-for-cc that referenced this pull request Nov 19, 2025
fix: no "Start Task" when config specs dir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants