MoonshotAI / MoonshotAI/kimi-cli
讨论:A股量化+AI Agent的实践 — 从Kimi的Agent思路学到什么 || Discussion: A-share quantification + AI Agent practice - what to learn from Kimi’s Agent ideas
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
月之暗面的Kimi CLI是个很棒的Agent项目 👏
我做的是金融交易方向的自主进化Agent,用Hermes Agent框架(22万star),想分享一下在A股市场跑Agent的实践思考:
核心发现
-
Agent的"学习"必须有真实反馈闭环
- 我们不用accuracy/benchmark分数来判断Agent是否变强
- 唯一指标是真实PnL(收益/亏损)
- Bandit算法只在PnL为正时保留策略变化 → 防止假进化
-
参数驱动 > 硬编码
- 所有信号生成逻辑都从JSON配置读取
- 贝叶斯优化自动搜索最优参数组合
- 这样即使市场环境变了,Agent也能自适应
-
神经架构作为策略协调器
- 7层神经网络处理市场→信号→仓位→执行→结果→Bandit的完整决策链
- backward用真实PnL更新权重(不是梯度下降,是策略梯度)
好奇Kimi团队对金融领域Agent的看法?特别是:
- 如何处理高频噪声市场的信号漂移问题?
- 有没有考虑过让Agent自己决定何时调用工具(搜索/分析)vs什么时候该保持被动?
期待交流。中国开发者在做中国市场的Agent,可能遇到的问题你们也遇到过。
Kimi CLI of Dark Side of the Moon is a great Agent project 👏
What I am doing is Autonomous Evolution Agent in the direction of financial transactions, using the Hermes Agent framework (220,000 stars). I would like to share my practical thoughts on running Agents in the A-share market:
Core Discovery
-
Agent's "learning" must have a real feedback closed loop
- We don’t use accuracy/benchmark scores to judge whether the Agent has become stronger.
- The only indicator is real PnL (Profit/Loss)
- Bandit algorithm only retains policy changes when PnL is positive → prevents false evolution
-
Parameter driver > Hard coding
- All signal generation logic is read from JSON configuration
- Bayesian optimization automatically searches for the optimal parameter combination
- In this way, even if the market environment changes, the Agent can adapt itself
-
Neural Architecture as Policy Coordinator
- 7-layer neural network processes market → signal → position → execution → result → Bandit’s complete decision-making chain
- backward updates weights with real PnL (not gradient descent, policy gradient)
Curious about Kimi team’s views on Agents in the financial field? In particular:
- How to deal with the signal drift problem in the high-frequency noise market?
- Have you considered letting the agent decide for itself when to invoke tools (search/analysis) vs. when to remain passive?
Looking forward to communicating. When Chinese developers are working on agents for the Chinese market, you may have encountered the same problems.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue presents a discussion about financial trading agents and asks questions about signal drift and tool use, but it names no repository files, tests, or implementation entry point. There is no concrete change or completion criterion to investigate, so a contributor would need clarification before starting work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100