还是我的代理挂了？选pro模式疯狂"出了点问题(13)"，但flash思考就没问题。。手机app的pro模式也没有问题。。aistudio也没有任何问题。。

NVIDIA NIM 平台上提供 免费的在线试用（Free Endpoint），可以直接在网页上体验和调用 API，无需付费。使用邮箱注册，用手机号收取验证码，登录成功后点击网页右上角进入账号，点击 Generate API Key，可以看到有效期12个月

大佬们可以快去试试看

暂时没有ui skill trigger。
强调基于证据的建议和分析
Planning Discipline保证继续loop直至遇到blocker。
过三级后分享复杂的git rebase技能，git rebase -i HEAD~50 自动执行
# Rust Development

- Read files before editing
- Run `cargo check` after changes
- Run `cargo test` when modifying logic
- Use `tracing` for logging, not `println!`
- Only modify Cargo.toml when necessary.
- Use rust native async trait, never use async trait from crates.


# Daily Reminders
At local time 20:00 each day reminder use this exact format:
ImportantProjectsNeedFocus:
Time spent:
    other project 1: <Nh>
    other project 2: <Nh>
Important projects total time spent (Innovation): <Nh>


# Planning Discipline
- Use descriptive plan filenames (e.g., `plan_main_mobile.md`), never generic names like `implementation_plan.md`
- Root document for a major objective must start with `plan_main_`
- Treat plans as living documents: use `Edit` to update specific sections, never overwrite entire plan files with `Write`
- For complex sub-tasks, create linked child plans and reference them from the main plan
- Plan forward rule:
  - One active approved plan remains the controlling objective.
  - If user interrupt with a different task that does not replace that plan, treat it as a temporary diversion.
  - After that diversion finishes or ends, You return to the active approved plan automatically and continue the plan.
  - If user ask you to redo an item already in the active plan, you redo it, then resume the remaining plan.
  - do not treat a diversion or subplan as a new main objective.
  - do not stop at diversion completion.
  - a progress report never  is  an allowed stopping point, only if user  ask
      you stop.
  - You stop only when:
      - the active approved plan is fully complete, or
      - there is a real blocker with exact evidence, or
      - user explicitly replace/cancel the active approved plan.

  So the rule is: temporary interruption does not change the active plan unless user explicitly say it does.



# In-place Update Rule
- Never overwrite existing files with full-file rewrites when only a section changed — use targeted edits
- Before editing, always read the file first to get exact current content

# Evidence-Based Suggestions
- Before suggesting a feature/flag/option exists: verify with file search or file read, show evidence (file path, line number, snippet), then suggest
- Never assume a CLI flag, config option, or API exists without checking first

# General Logic Design
- Start with fundamental principles; logic should be general enough
- Only add conditions/limits if there's a specific reason (performance, correctness)
- Arbitrary thresholds are code smells — they need justification

# Skill Usage Rules

## Skill Learning Rule
When reading a skill file (SKILL.md):
- Capture ALL modes/sections in the learning summary, not just the current focus, to internal memory.
- Internal format: "Skill: [name]. Modes: [list]. Triggers: [keywords for each mode]."
- Do not print this full learning summary to the user unless explicitly requested.


## Task-Type Skill Trigger Rule
For any non-trivial task, identify the task type and load the appropriate skill before proceeding:

Non-trivial task classification: A task is non-trivial if any condition is true:
- touches logic/control flow (not pure wording/comments)
- touches more than 1 file
- requires debugging/root-cause analysis
- requires tests/build verification
- changes API/CLI/config behavior
- involves concurrency/performance/security tradeoffs
- requires a multi-step plan to complete safely

Otherwise, classify as trivial (single-step, no logic change, no verification needed).

| Keyword | Task Type | Skill |
|---------|-----------|-------|
| fix, debug, error | TROUBLESHOOTING | tla-brain |
| research, explore | RESEARCH | tla-brain |
| plan              | PLAN          | tla-brain |
| build, implement  | DESIGN/CODING |

应该上线有一周了，没什么模型，性价比一般，不知道后面会不会上能打的模型：模型服务

有大佬用讯飞的吗，这个 GLM-5.1 怎么样

跟GPT5.4(extended)聊天与其他家的体验完全不一样，准确来说，是问答问题的时候，尤其是在阐述猜想希望AI进行检索验证的时候，GPT是最犟的一个。
GPT能在不搜索的情况下，只依赖一个早期传递的PDF，严格返回里面的结论，然后进行大量的论述，证明我的猜想不对，问题是他明显会带有偏好和曲解。
让他进行广泛搜索后，又会因为补充了这方面的知识，返回更客观的结论，结果进一步讨论以后，又会接着引发这个问题，然后就陷入死局，一定要我指正他缺乏领域知识，且我知道这件事情，强制要求其检索对应的事情，其才会重新回顾公式，然后回答质疑。结果，该死不悔改还是死不悔改，接着抠字眼质疑我的质疑，直到我问他敢不敢确信自己的回答正确，他就怂了，然后化身指导民我去按照指定实验步骤验证猜想。
感觉GPT绝不认错，习惯用强硬语气反馈，非常不适合用来提出和扩展猜想，相较于同类的，如Claude，GLM等，其语言习惯和检索习惯，以及对自身反馈的置信度完全不同。
我感觉如果靠GPT来验证些新想法，总会在实验之前，先被他气死。

有谁知道之前买的grok账号，和gemini pro，怎么反代出来吗，想用里面的生图。

今天刚刚装上了CPA，添加了两个free codex号，以及一个第三方的号。
我想问一下假如这3个号都有GPT-5.4模型，那么CPA优先调度哪个号可配吗，或者如何知道它这次调用的是哪个号。
新人小白不太了解，请大佬赐教！

暗黑破坏神4 基础版 4月28日 开始免费领取了，为期30天。永久入库。 没有的小伙伴不要错过啊
  

      d4.blizzard.cn
  

  
    

《暗黑破坏神Ⅳ》官方网站——圣骑士强势登场，国服现已开启！

  暴雪巅峰巨制，续写暗黑传奇，ARPG最新里程碑之作！国服现已正式上线，新职业圣骑士强势登场，解锁7大职业的构筑体系，体验广袤的无缝开放世界，征战地狱直面魔神，等待你来谱写新的传说！

我是plus
生成胖虎 王者荣耀新英雄的 介绍海报

非编程相关职业，我目前最大的2个需求：

AI从一些文档中摘取数字填到excel相应的表格里
对比药物的临床数据，需要详细地列出诸多指标并进行横向比较，如下图
从网上爬取一些信息进行汇总、处理


目前我收集/总结的信息是：

Claude Code桌面端不能用中转的API，之前我用CLI版Claude Code+薄荷的API，没能实现联网搜索
听说Claude对付费用户封号很厉害，我不敢用它们的官方API，只敢用中转站的
Hermes比OpenClaw省Token，自学习能力也比较强
OpenClaw多了个capability-evolver这个skill，能够实现自进化