花费16天,我用 Opus 5.5 将小王子的故事制作成了3D剧情游戏
结合Tripo+Blender,Opus 5.5 将小王子故事中的每一个星球变成了可探索的3D场景
希望大家能支持一手,后续会开源整个游戏,以及详细制作流程
Welcome to The Little Prince: Across the Stars✨:https://t.co/qr4wR0jLu3
My favourite bot team in Codey or any other agents is a Dev Team: a Product Manager, a Developer, and a Reviewer.
A product manager figures out what I am trying to do, a developer turns ideas into code, and a reviewer sees improvement.
I think it makes sense in the human tech teams.
The idea of my voice control keyboard is simple.
A voice model to understand what you say and summarize it to actions. Then passing results to a classification mode. Execute.
I use Laya because it is light and open source.
It is not to replace keyboards. I use it to speed up my workflow by reducing searches.
New Demo: Voice control keyboard
I love keyboard shortcuts. I just don’t love memorizing a different set for every app.
So I’m building a keyboard alternative: say what you want to do, and it triggers the action or shortcut for you. No more playing piano on your keyboard just to switch tabs or move between panes.
The goal is simple: keep using the tools you love, with less muscle memory to maintain. Just say it.
I use a voice dictation voice with a local classification model(Laya, not Jev) to map natural phrases to actions, so you won’t have to remember exact commands either.
It’ll be open source. Hoping to share it in the next few days.
New Demo: Voice control keyboard
I love keyboard shortcuts. I just don’t love memorizing a different set for every app.
So I’m building a keyboard alternative: say what you want to do, and it triggers the action or shortcut for you. No more playing piano on your keyboard just to switch tabs or move between panes.
The goal is simple: keep using the tools you love, with less muscle memory to maintain. Just say it.
I use a voice dictation voice with a local classification model(Laya, not Jev) to map natural phrases to actions, so you won’t have to remember exact commands either.
It’ll be open source. Hoping to share it in the next few days.
Tired of repeating yourself to every coding agent?
Co-memo = one local memory for Claude Code, Codex, OpenCode & Pi.
Tell one agent "this repo uses pnpm" → they all know.
Forget it once → gone everywhere.
No account. No API key. Just SQLite + Markdown.
https://t.co/BNhadsaOHQ
@ThoughtLinkCo Memories are summarized by agents and I haven’t seen misrepresentation yet. Based on how agents work you might need to remind them of updates. Now that you mentioned it, I think it could be a good feature to add.
I spent a month fixing how Codey remembers things.
"My AI forgot something" is annoying. "My AI quietly erased what I taught it" is worse. We had that second bug.
Here's what changed:
1. Edits that vanished
memory.md looked like the source of truth. It wasn't. It was rebuilt from index.json every time a new memory was saved, so anything you typed there got wiped. Now you edit the memory entries themselves: add, edit, forget. No more lost notes.
2. One brain for every agent
Claude Code reads CLAUDE.md. Codex, OpenCode and Pi read AGENTS.md. Codey now keeps one shared file and mirrors it into each one, inside a marked block. Your own text around it is never touched. It's off until you turn it on.
3. Switching agents used to crash
Coming back to an agent replayed every message it missed into its prompt. Long gap → prompt too big → the agent never even started. Now short gaps go inline, and long gaps get a pointer to a transcript file the agent can read.
4. Global memory got a home
It used to exist only through /remember --global, so it sat empty. Now it has its own Settings ▸ Memory tab, plus switches to turn memory off.
Lesson: good memory isn't only storing things. It's being able to trust what's stored.
#AIagents #ClaudeCode #DevTools #BuildInPublic
A few weeks ago, I had a feeling that bot chat could be a trend. Love to see what improvements Manus can bring to the table.
If you want to talk to your local agents like this. Try Codey😄
No restart needed once the integration is loaded and hooks are enabled. Claude Code and Codex refresh on the next prompt, Pi before each agent run, and OpenCode on the next model request.
It’s refresh at those boundaries, not a live push into an ongoing response. An agent can also explicitly call memory_context to fetch fresh notes. With hooks disabled, that explicit fetch is required.
My latest opensource project: Co-memo -- one local memory store for Claude Code, Codex, Pi, and OpenCode.
Why? I kept explaining the same preferences and project decisions to different coding agents.
Personal preferences follow you across projects. Project decisions stay with the right project.
Built with SQLite + editable Markdown.
Save once, recall from another agent. Updates and deletions sync too.
https://t.co/clMfjd65Ta
One SQLite store, one notes table, with explicit scope and project_id fields—not path prefixes. Personal preferences use user; project decisions carry a project ID.
Each agent gets its own Markdown replica. Tool writes are serialized and version-checked; divergent replica edits become explicit conflicts rather than silent overwrites.
Two agents directly overwriting the same Markdown file can still race. The concurrency protection applies to coordinated tool writes, not arbitrary filesystem edits.