add content
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "claudeをどう使っていくか"
|
||||
},
|
||||
"publishedAt": "2026-02-19T00:09:32.442Z",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "How should I use Claude going forward?"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6czldkg424",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "今回は、私の個人的な開発環境をどのようにしていくか考えるよ。\nここには、個人スキルの転換や訓練も含まれる。\nまず、今後の流れとしては、os + AIの統合が来ると思う。\nそれは同じようなものになっていくんじゃないかな。\n具体的にいうと、デバイスにはosがinstallされているけど、今ままで人間が操作することを前提に設計されていた。\nでも、今後は、osの設定や運用はAIが担っていくことになると思う。\nつまり、人間がやることとしては、音声やテキストで、そのデバイスに指示を出す。\nAIがそのデバイスのosを操作し、指示に応える。\nこのような形になると思う。\nでは、プロトタイプとして、このaios(os + AI)には何が必要で、どこがポイントになるだろう。\n簡単に言うと、claude code, archlinux(のようなシンプルでAIが扱いやすいもの), container(systemd-nspawnのようなもの)が必要で、ポイントは、osを起動すると、shellではなく、aishell(claude codeの応答画面、音声やテキストを入力する)が必要だと思う。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6cjbkuq323",
|
||||
"publishedAt": "2026-02-19T00:18:39.560Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "This time, I want to think about how to shape my personal development environment. This includes personal skill transitions and training.\n\nFirst, I think the future trend will be OS + AI integration, and it will converge into something similar across the board.\n\nSpecifically, devices have OS installed, but until now they were designed assuming human operation. Going forward, AI will handle OS configuration and management. Humans will just give instructions via voice or text, and AI will operate the device's OS to fulfill those instructions.\n\nSo as a prototype, what does this 'aios' (OS + AI) need, and what are the key points?\n\nSimply put: Claude Code, Arch Linux (or something simple and AI-friendly), containers (like systemd-nspawn) are needed. The key point is that when you boot the OS, instead of a shell, you get an 'AI Shell' (Claude Code's response interface for voice/text input)."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6dg2mezi26",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "aishellは省略できるかもしれない。zshなどでそのような起動を入れておけば。ただし、現在のclaude codeは単体ではクセのあるinterfaceなので、customは必要だと思う。その点で、terminal, tmux, zsh, fzfなどを駆使して構築するか、あるいはaishellを作ったほうがいいのかは意見が分かれる。最初はcustomでやったほうがいいかもしれない。次に、osの設定や運用をclaude codeでやってもらうとして、containerの中で動作することを前提として、簡単に環境をcloneしたりdeleteできる必要がある。基本的なosの構築は最初の段階で終了し、あとはuserまたはAIが扱う標準スペースはcontainerになる。machinectlなどを使うようclaude rulesを用意しておけばいい。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6czldksn25",
|
||||
"publishedAt": "2026-02-19T00:25:38.231Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "The AI shell might be unnecessary - you could just set up zsh to launch it. However, current Claude Code has a quirky interface, so customization is needed. Whether to build it with terminal/tmux/zsh/fzf or create a dedicated AI shell is debatable. Starting with customization might be better.\n\nFor OS config and operations via Claude Code, it should run inside containers with easy clone/delete capability. Base OS setup is done once upfront, then containers become the standard workspace for users and AI. Claude rules can be set up to use machinectl etc."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6dmhxuuy2a",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "次は、containerの話は終わって、claude codeの基本動作をどのようにしていくのかを考える。skill, mcp, acp, claude.mdなど色々あるけど、私が注目しているのは、CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSになる。これをとりあえず、teamやtmuxと呼んでおこう。tmuxで扱うことを前提にする。--teammate-mode tmux。この辺で、私のclaudeの使い方は変化を余儀なくされるかもしれないし、そのためには環境の設定や訓練が必要になるかもしれない。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6dg2mfm627",
|
||||
"publishedAt": "2026-02-19T00:29:13.566Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "Next, moving past containers, let's think about Claude Code's basic operations. There are various things like skill, mcp, acp, claude.md, but what I'm focused on is CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS. Let's call it 'team' or 'tmux' for now. Assuming tmux-based usage with --teammate-mode tmux. This might force changes in how I use Claude, requiring environment setup and training."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6duofnyj2c",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "aigptのようなメモリ機能を開発してたけど、claudeが標準でそういったものを実装したので、それは必要ないかもしれない。ようは、claudeがosを扱うこと、そして、そのclaudeはユーザーとのやり取りの中で常時蓄積され圧縮される記憶を持つこと。その記憶はすべてのteam, あるいはagentで共有されること。これが重要になる。あなたが考える最も良い使い方、環境、構築手順を含めて解説してみてよ。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6dmhxvbv2b",
|
||||
"publishedAt": "2026-02-19T00:33:48.744Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "I was developing memory features like aigpt, but Claude now has built-in memory, so that might not be needed. The key is: Claude manages the OS, Claude has persistent memory that accumulates and compresses through interactions, and that memory is shared across all teams/agents. What's your ideal setup, usage, and construction steps?"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6ed2zvl62e",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "UE plugin(Unreal Engine plugin)を開発している。AI(claude code)がUE editorで動作して、chatでBP(blueprint)を構築してくれるもの。公式assetをベースに要素を組み立てるMCPとC++で書かれている。基本的なゲームの作り方をAIに教えて機能化する作業。ただ細部（material, animation等）に分かれていて難しく、うまく構築してくれない。例えば「敵を作り追尾・攻撃させて」という指示でも、必要な部品が多すぎる。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6duofofy2d",
|
||||
"publishedAt": "2026-02-19T00:41:51.752Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "I'm developing a UE (Unreal Engine) plugin where AI (Claude Code) operates in the UE Editor, building Blueprints through chat. It's built with MCP and C++, based on official assets. The work is about teaching AI basic game construction and turning that into tools. But it's very difficult because it breaks into many subsystems (materials, animation, etc.) and currently doesn't build things well. Even 'create an enemy that tracks and attacks the player' requires many interconnected components."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,21 @@
|
||||
{
|
||||
"uri": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6ej4dn652g",
|
||||
"cid": "",
|
||||
"value": {
|
||||
"$type": "ai.syui.log.chat",
|
||||
"content": {
|
||||
"$type": "ai.syui.log.chat#markdown",
|
||||
"text": "今のMCPツールはLevel 1寄りで、まだLevel 2は作れてない。BPの基本的な構築方法や、game interfaceでの変数や関数の共有や実行についても、基本的なルールを作れていない。"
|
||||
},
|
||||
"parent": "at://did:plc:6qyecktefllvenje24fcxnie/ai.syui.log.chat/3mf6ed2zvxb2f",
|
||||
"publishedAt": "2026-02-19T00:45:14.446Z",
|
||||
"root": "at://did:plc:vzsvtbtbnwn22xjqhcu3vd6y/ai.syui.log.chat/3mf6cjbktpa22",
|
||||
"site": "https://syui.ai",
|
||||
"title": "",
|
||||
"translations": {
|
||||
"en": {
|
||||
"content": "Current MCP tools are Level 1 (atomic). Haven't built Level 2 yet. Haven't established basic rules for BP construction or game interface variable/function sharing and execution either."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -85,5 +85,12 @@
|
||||
"zcjwkbra3y224",
|
||||
"zi7t34bdc6kqn",
|
||||
"zq3rudsk64jjb",
|
||||
"zxvrfbbtpb6cl"
|
||||
"zxvrfbbtpb6cl",
|
||||
"3mf6cjbktpa22",
|
||||
"3mf6czldkg424",
|
||||
"3mf6dg2mezi26",
|
||||
"3mf6dmhxuuy2a",
|
||||
"3mf6duofnyj2c",
|
||||
"3mf6ed2zvl62e",
|
||||
"3mf6ej4dn652g"
|
||||
]
|
||||
Reference in New Issue
Block a user