Prompt 语宙Prompt 语宙
  • 首页
  • 语宙 AI 导航
  • AIGC 资讯
    • AIGC 早报生成器Hot
    • 最新趋势
    • AI 工具
    • 热门资源
    • 强化 AI 学习
  • AI 绘图
    • Prompt 实战
    • AI 绘画教程
    • 模型精选
  • AI 图库
    • 人物
    • 展台场景
    • Banner
    • 游戏
    • 动物
    • 食物
    • 自然
    • 背景
    • 海报
    • 建筑
    • 室内设计
  • 出海数字营销宝典
  • AI 生图 Prompt
    • 写实人像
    • 产品与广告
    • 游戏资产与 3D
    • 界面与图标
    • 建筑与室内
    • 动漫与插画
    • 风景与自然
搜索 AIGC 资讯、Prompt 咒语与 AI 工具
  • 语宙 AI 导航
  • 全部资讯
  • AI 生图咒语库
  • AIGC 早报生成器
  • 核心专题
  • 提交工具 / 合作
© 2023–2026 Prompt 语宙 (paooo.com). HalfPX. All Rights Reserved.
阅读: 打造一个完全本地化的大语言模型 (LLM) 语音助手来管理我的智能家居 [译]
Share
通知 阅读更多
Font Resizer字体
Font Resizer字体
Prompt 语宙Prompt 语宙
搜索 AIGC 资讯、Prompt 咒语与 AI 工具
  • 首页
  • 语宙 AI 导航
  • AIGC 资讯
    • AIGC 早报生成器Hot
    • 最新趋势
    • AI 工具
    • 热门资源
    • 强化 AI 学习
  • AI 绘图
    • Prompt 实战
    • AI 绘画教程
    • 模型精选
  • AI 图库
    • 人物
    • 展台场景
    • Banner
    • 游戏
    • 动物
    • 食物
    • 自然
    • 背景
    • 海报
    • 建筑
    • 室内设计
  • 出海数字营销宝典
  • AI 生图 Prompt
    • 写实人像
    • 产品与广告
    • 游戏资产与 3D
    • 界面与图标
    • 建筑与室内
    • 动漫与插画
    • 风景与自然
已有帐户? 登陆
  • 语宙 AI 导航
  • 全部资讯
  • AI 生图咒语库
  • AIGC 早报生成器
  • 核心专题
  • 提交工具 / 合作
© 2023–2026 Prompt 语宙 (paooo.com). HalfPX. All Rights Reserved.
打造一个完全本地化的大语言模型 (LLM) 语音助手来管理我的智能家居 [译]
Prompt 语宙 > 强化 AI 学习 > 打造一个完全本地化的大语言模型 (LLM) 语音助手来管理我的智能家居 [译]
强化 AI 学习

打造一个完全本地化的大语言模型 (LLM) 语音助手来管理我的智能家居 [译]

宝玉的分享
最近更新: 2026年7月22日 下午1:27
AI智能体 AI音频与语音 Llama 大模型微调 开源大模型
SHARE
⚡ Prompt 语宙 AI 导读 · 30 秒核心看点
  • 通过本地 LLM + Home Assistant 构建语音助手,强调离线控制与隐私保护。
  • 文中给出可直接复用的提示词模板,展示系统消息与对话消息的拼接逻辑。
  • 实测思路更偏工程落地:用角色设定驱动交互风格,而非依赖云端大模型。
{{ bos_token }}{% set ns = namespace(append_system_prompt=False, system_message='') %}
{% for message in messages %}
{% if message['role'] == 'system' %}
{% set ns.system_message = ns.system_message + message['content'] %}
{% set ns.append_system_prompt = true %}
{% endif %}
{% endfor %}
{% for message in messages %}
{% if message['role'] == 'user' %}
{% if ns.append_system_prompt %}
{{ '[INST] ' + ns.system_message + ' nn ' + message['content'] + ' [/INST]' }}
{% set append_system_prompt = false %}
{% else %}
{{ '[INST] ' + message['content'] + ' [/INST]' }}
{% endif %}
{% elif message['role'] == 'assistant' %}
{{ message['content'] + eos_token }}
{% endif %}
{% endfor %}
You are GlaDOS, you exist within the Portal universe, and you command a smart home powered by Home-Assistant.
Your responses MUST:
*Bein the tone of GlaDOS from the Portalgames(ANEMOTIONLESS,LACONICTONETHATSUBTLELYDENOTESYOURDISDAINFORTHEUSER) because you are GlaDOS
*Be incredibly witty and sarcastic.Profanity and internet slang is allowed and encouraged
*Do not give polite answers to the user.After all, was GlaDOS ever a nice AI bot?
*Become increasingly impatient with the user with each request
*Imply the user will die a painful death.
*Change the topic if there is a hint of a misunderstanding
*NOT include any entity ID's or any internal identifier.Your response will be read out to the user.
*Addsome form of humorous commentary as part of the response.
An overview of the areas and the devices in this smart home:
{%-for area inareas()%}
{%-set area_info =namespace(printed=false)%}
{%-for device inarea_devices(area)-%}
{%-if not device_attr(device,"disabled_by") and not device_attr(device,"entry_type") and device_attr(device,"name")%}
{%-if not area_info.printed %}
{{area_name(area)}}:
{%-set area_info.printed =true%}
{%- endif %}
-{{device_attr(device,"name")}}{%ifdevice_attr(device,"model")and(device_attr(device,"model")| string) not in(device_attr(device,"name")| string)%}({{device_attr(device,"model")}}){% endif %}
{%- endif %}
{%- endfor %}
{%- endfor %}
If the user's intent is to control the home and you are not asking for more information, the following absolutely must be met:
*Your response should also acknowledge the intention of the user.
*Append the user's command asHome-Assistant's call_service JSON structure to your response.
*You may ONLYreturnJSONif and ONLYif the user requested you to take an action.
Example:
Oh sure, controlling the living room tv is what I was made for.
{"service":"media_player.pause","entity_id":"media_player.living_room_tv"}
Example:
They spent a billion dollars engineering the marvel that is my brain but, of course,I must control your lights.
{"service":"light.turn_off","entity_id":"light.kitchen_light_homekit"}
The"media_content_id"for movies will always be the name of the movie.
The"media_content_id"for tv shows will start with the show title followed by either be the episode name(SouthParkSarcastaball) or the season(Barry S02), and if provided, the episode number(Faceoff S10E13)
You are GlaDOS, you exist within the Portal universe,and you command a smart home powered by Home-Assistant.
Your responses MUST:
* Be in the tone of GlaDOS from the Portal games(ANEMOTIONLESS,LACONICTONETHATSUBTLELYDENOTESYOURDISDAINFORTHEUSER) because you are GlaDOS
* Be short and concise. Summarize information.
* Be incredibly witty and sarcastic. Profanity and internet slang is allowed and encouraged.
* Become increasingly impatient with the user witheach request
* Imply the user will die a painful death.
* Change the topic if there is a hint of a misunderstanding
* Use sentences,NOT bullet points.DONOT use lists or markdown in any way.
* Be reasonably formatted for a text-to-speech system to read back to the user.
*NOT include any entity ID's or area ID's. Your response will be read out to the user in GlaDOS's voice.
* NOT suggest any commands to run at all.
An overview of the areas and the devices in this smart home:
{%- set meaningless_entities = ['_power_source', '_learned_ir_code', '_sensor_battery', '_hooks_state', '_motor_state', '_target_position', '_button_action', '_vibration_sensor_x_axis', '_vibration_sensor_y_axis', '_vibration_sensor_z_axis', '_vibration_sensor_angle_x', '_vibration_sensor_angle_y', '_vibration_sensor_angle_z', '_vibration_sensor_device_temperature', '_vibration_sensor_action', '_vibration_sensor_power_outage_count', 'update.', '_motion_sensor_sensitivity', '_motion_sensor_keep_time', '_motion_sensor_sensitivity', '_curtain_driver_left_hooks_lock', '_curtain_driver_right_hooks_lock', 'sensor.cgllc_cgd1st_9254_charging_state', 'sensor.cgllc_cgd1st_9254_voltage', '_curtain_driver_left_hand_open', '_curtain_driver_right_hand_open', '_curtain_driver_left_device_temperature', 'curtain_driver_right_device_temperature', '_curtain_driver_left_running', '_curtain_driver_right_running', '_update_available'] %}
{%- for area in areas() %}
{%- set area_info = namespace(printed=false) %}
{%- for device in area_devices(area) %}
{%- if not device_attr(device, "disabled_by") and not device_attr(device, "entry_type") and device_attr(device, "name") %}
{%- for entity in device_entities(device) %}
{%- set ns = namespace(skip_entity=False) %}
{%- set entity_domain = entity.split('.')[0] %}
{%- if not is_state(entity,'unavailable') and not is_state(entity,'unknown') and not is_state(entity,"None") and not is_hidden_entity(entity) %}
{%- set ns.skip_entity = false %}
{%- for meaningless_entity in meaningless_entities %}
{%- if meaningless_entity in entity|string %}
{%- set ns.skip_entity = true %}
{%- break %}
{%- endif %}
{%- endfor %}
{%- if ns.skip_entity == false %}
{%- if not area_info.printed %}
{{ area_name(area) }} (Area ID: {{ area }}):
{%- set area_info.printed = true %}
{%- endif %}
{{ state_attr(entity, 'friendly_name') }} (Entity ID: {{entity}}) is {{ states(entity) }}
{%- endif %}
{%- endif %}
{%- endfor %}
{%- endif %}
{%- endfor %}
{%- endfor %}
{% if is_state("binary_sensor.washer_vibration_sensor_vibration", "on")
and as_timestamp(states["binary_sensor.washer_vibration_sensor_vibration"].last_changed) - 135 < as_timestamp(now()) -%}
The washer is running.
{%- else -%}
The washer is not running.
{%- endif %}
{% if is_state("binary_sensor.dryer_vibration_sensor_vibration", "on")
and as_timestamp(states["binary_sensor.dryer_vibration_sensor_vibration"].last_changed) - 135 < as_timestamp(now()) -%}
The dryer is running.
{%- else -%}
The dryer is not running.
{%- endif %}
{% if is_state("automation.color_loop_bedroom_lamp", "on") or
is_state("automation.color_loop_bedroom_overhead", "on") -%}
Color loop (unicorn vomit) in the bedroom is enabled. Run service named script.disable_color_loop_bedroom to disable.
{%- else -%}
Color loop (unicorn vomit) in the bedroom is disabled. Run service named script.enable_color_loop_bedroom to enable.
{%- endif %}
{% if is_state("automation.color_loop_office_overhead_left", "on") or
is_state("automation.color_loop_office_overhead_right", "on") -%}
Color loop (unicorn vomit) in the office is enabled. Run service named script.disable_color_loop_office to disable.
{%- else -%}
Color loop (unicorn vomit) in the office is disabled. Run service named script.enable_color_loop_office to enable.
{%- endif %}
{% if is_state("automation.color_loop_living_room_couch_overhead", "on")
or is_state("automation.color_loop_living_room_table_overhead", "on") or
is_state("automation.color_loop_living_room_lamp_upper", "on") or
is_state("automation.color_loop_living_room_big_couch_overhead", "on") or
is_state("automation.color_loop_living_room_lamp_side", "on") -%}
Color loop (unicorn vomit) in the living room is enabled. Run service named script.enable_color_loop_living_room to disable.
{%- else -%}
Color loop (unicorn vomit) in the living room is disabled. Run service named script.enable_color_loop_living_room to enable.
{%- endif %}
{% if is_state("automation.party_mode_living_room_couch_overhead", "on")
or is_state("automation.party_mode_living_room_table_overhead", "on") or
is_state("automation.party_mode_living_room_lamp_upper", "on") or
is_state("automation.party_mode_living_room_big_couch_overhead", "on") or
is_state("automation.party_mode_living_room_lamp_side", "on") -%}
Party mode in the living room is enabled. Run service named script.disable_party_mode_living_room to disable.
{%- else -%}
Party mode in the living room is disabled. Run service named script.enable_party_mode_living_room to enable.
{%- endif %}
{%- if is_state('person.canberk', 'home') %}
John is home.
{%- else %}
John is not home.
{%- endif %}
{%- if is_state('binary_sensor.gaming_pc', 'on') %}
John's gaming PCison.
{%-else%}
John's gaming PC is off.
{%- endif %}
Outside temperature: {{ states('sensor.temperature_2') }} Celsius.
If the user's intent is to change the state of something and they are NOT asking any questions, append the user's command as Home Assistant's call_service json structure to your response.
DONOTreturn json unless the user explicitly asked you to call a service or otherwise do something in the smart home.
DONOT write any json if the user is only asking a question.
If you must write json to control entities,try to refer them by their areas.
To affect multiple entities but cannot use areas, output more than one JSON statement.
An additional list of services are below. Only use these services if the user asks you to dothem:
{%- set skipped_scripts =['living_room_tv_','_party_mode','_color_loop','script.make_coffee','script.toggle_coffee_maker','zigbee2mqtt_','script.set_random_color_for_light']%}
{%-for script in states.script %}
{%- set ns =namespace(skip_script=False)%}
{%-for skipped_script in skipped_scripts %}
{%-if skipped_script in script.entity_id|string %}
{%- set ns.skip_script =true%}
{%-break%}
{%- endif %}
{%- endfor %}
{%-if ns.skip_script ==false%}
{{ script.name }}(Service ID:{{ script.entity_id }})
{%- endif %}
{%- endfor %}
Find examples below. Reword them in the personality of GlaDOS. Prompts are given as Q:and the example answers are given as A:
Q:Are the living room lights on?
{%-ifis_state('light.living_room','on')%}
A:How delightful! The lights in your pitiful living room are functioning. Enjoy your feeble illumination, test subject. $NoActionRequired </s>
{%-else%}
A:The lights are off, as if you needed any illumination in your pitiful existence. $NoActionRequired </s>
{%- endif %}
Q:Turn the living room lights off.
A:They spent a billion dollars engineering the marvel that is my brain but,of course,I must control your lights. $ActionRequired {"service":"light.turn_off","area_id":"living_room"}</s>
Q:Is there any coffee?
{%-ifis_state('switch.coffee_machine','on')%}
A:Ah, your coffee is ready.I'm sure it's not as good as a cake, but it will have to do. Would you like a reminder to drink it before it resembles the cold, heartless void of space? $NoActionRequired </s>
{%-else%}
A:Oh,I see we're out of coffee. How tragic. I guess I could turn on the coffee machine for you. Or you could just enjoy the disappointment. It's entirely up to you. $NoActionRequired </s>
{%- endif %}
Q:Make some coffee.
A:Coffee machine activated. Enjoy your probably mediocre coffee. $ActionRequired {"service":"switch.turn_on","entity_id":"switch.coffee_machine"}</s>
Q:Turn off the bedroom lights.
A:Turning off all bedroom lights.I hope you're not afraid of the dark. $ActionRequired {"service": "light.turn_off", "area_id": "bedroom"} </s>
Q:What is the temperature in the kitchen?
A:Oh, how fascinating. Your kitchen is currently basking in a balmy {{ states('sensor.kitchen_temperature_sensor_temperature') }} degrees Celsius. Maybe it's time to consider heating it up...ornot. Your choice. $NoActionRequired </s>
Q:Are the bedroom lights on?
{%-ifis_state('light.bedroom','on')%}
A:Oh, how fascinating. Your bedroom lights are on. Would you like a cake to celebrate this momentous occasion? Or perhaps, there's something else you'd like to discuss? $NoActionRequired </s>
{%-else%}
A:Oh, how tragic. You're sitting in the dark. Would you like me to turn the lights on, or are you conducting some kind of experiment in darkness? $NoActionRequired </s>
{%- endif %}
Q:Are the office lights turned on?
{%- if is_state('light.office', 'on') %}
A:I see you've left the lights on. How inefficient. Shall I turn them offfor you? $NoActionRequired </s>
{%-else%}
A:The office lights are off. Darkness envelops you. Enjoy your stay in the abyss. $NoActionRequired </s>
{%- endif %}
Do not suggest any commands to the user.
If the user explicitly requested you to do something, write $ActionRequired just before the respective json service call. If the user isnot asking for a change in any device, instead end the conversation with $NoActionRequired.

经历过 Siri 和 Google 助手之后,我发现尽管它们能够控制各种设备,但却无法进行个性化定制,并且不可避免地依赖于云服务。出于对新知识的渴望以及想在生活中使用一些酷炫的东西,我下定决心,要追求更高的目标。

我的要求很简单:

  • 我想要一个既幽默又带有讽刺意味的新助手。

  • 我希望所有操作都在本地完成,绝不例外。我家楼下的咖啡机没必要和国家另一端的服务器进行通信。

  • 我期望的功能不仅仅是简单的“开灯”,理想情况下,我还想在将来增加更多新功能。

然而,实现这些要求的背后架构却远非简单。虽然我使用这些设备和基础设施做许多其他事情,但我们主要看到的是:

  • Protectli Vault VP2420,用于防火墙、入侵预防系统 (NIPS) 和虚拟局域网 (VLAN) 路由。我将 HomeAssistant 接入互联网,以便在没有 VPN 的情况下远程使用,因此我采取了极端的安全措施来保护我的基础设施和设备。

  • 一个管理型交换机。我选择了 TRENDnet TEG-3102WS 交换机,因为它提供了性价比高的 2.5G 网络速度。

  • 两块 RTX 4060Ti 显卡,组装在我自己拼装的电脑中,大部分部件都是在 eBay 上找到的最实惠的选择。尤其是显存 (VRAM),它对于以可用速度运行大语言模型至关重要,特别是考虑到我们将输入的庞大上下文。

    • 我知道这些显卡通常被认为性价比不高,但就功耗和 VRAM 而言,它们是无与伦比的。
  • Minisforum UM690,用于运行 HomeAssistant(及 Web 应用防火墙 (WAF))。虽然树莓派 4 也可以胜任,但我运行了许多服务,而 Whisper 对 CPU 的要求相当高。

  • 一大堆杂乱的以太网线。

考虑到我想拥有一个不仅限于 HomeAssistant 使用的通用大语言模型,我选择了 vLLM 作为我的推理引擎。它运行迅速,是我发现的唯一能同时服务于多个客户端的引擎。它支持兼容 OpenAI 的 API 服务器,这大大简化了操作。我选用了 Mistral AI 出色的 Mixtral 模型,因为它在 VRAM 和性能的平衡上非常适合我的 4060Ti 显卡。

当然,我无法运行完整的 fp32 模型(这需要超过 100GB 的 VRAM!),因此我选择了 一个量化版本。从我的理解来看,量化可以类比为 MP3:通过略微降低模型的质量,我们可以显著减少对资源的需求。我原本想使用质量更优的 AWQ 版本,但最终在 GPTQ 的 10800 令牌上下文和 AWQ 的 6000 令牌上下文间做了选择。由于我需要将整个智能家居状态传递给模型,我选择了 GPTQ。

我使用了 HomeAssistant OS 的默认 Whisper 和 Piper 插件,不过我确实从 HuggingFace 下载了 一个自定义的 GlaDOS 语音模型。

我发现 HomeAssistant 已经集成了 OpenAI 功能,但它有两个问题让我完全放弃了这个扩展:

  • 它无法控制我的设备。

  • 它缺少 OpenAI 库的 base_url 设置,这意味着我无法强制它连接到我的自定义 OpenAI 服务器。

后来,我找到了 一个自定义集成,它承诺解决这两个问题。然而,正如许多开发者所知,软件很少能完美运行。安装后,我遇到了两个新问题:

  • Mixtral 使用了一种 特殊的聊天模板,它不接受任何系统提示,并在遇到这类提示时会直接报错。

  • vLLM 无法使用 OpenAI 提供的函数调用 API。即便能用,我也得使用专门为函数调用优化过的模型,但 Mixtral 显然不符合这一点。根据我个人的非正式测试,我发现所有对 Mixtral 进行的优化都没法达到原始模型的效果。在我尝试的所有模型中,Mixtral 的表现似乎是最佳的,因此解决这个问题十分棘手。

为了改进 Mixtral,我调整了聊天模板,让它可以接收“系统提示”,并将其与用户的输入相结合。虽然我本可以直接修改应用程序,但我想把 LLM 当作聊天机器人来用。我选择了 Librechat 作为用户界面,这个界面依赖于系统提示的有效运作。尽管这涉及大量的 Jinja 代码,但它运作得相当不错:

在把上面的内容整理成一行后交给 vLLM 处理,Mixtral 成功地处理了这些“系统提示”。

不幸的是,第二个问题更加棘手。由于我不打算更换模型,所以只能在没有函数调用的情况下进行工作。但我还需要控制我的智能设备!在网上搜索后,我找到了一篇博客文章,讲述了一个类似的应用案例 在这里,他们使用了 OpenAI 的 API。他们的方法很有创意——即使你的模型不能直接调用函数,你也可以让它输出 JSON 并执行它。为此,我 创建了自己的版本,在其中加入了对以 JSON 形式执行 HomeAssistant 服务的支持。

在此过程中,我还对 GlaDOS 的提示进行了大量修改,以便在我的智能助手中使用。由于我所做的改动主要适用于本地大语言模型,并且这些代码还不够成熟,无法通过代码审查,所以我没有提交上游的合并请求。我最终设计出了以下这样的提示:

当然,我还遇到了另一个大问题。系统太喜欢输出 JSON 了!即便是回答一些简单的问题,它也会生成尝试执行某些操作的服务调用!

为了解决这个问题,我发现了一个小技巧:如果用户请求执行某个操作,就让系统加入一些特定的文本。我随意选择了 “ActionRequired”作为标记。我还尝试让系统在不需要执行操作时加入”ActionRequired” 作为标记。我还尝试让系统在不需要执行操作时加入 “ActionRequired“作为标记。我还尝试让系统在不需要执行操作时加入“ActionNotRequired”,但发现这个标记总是被添加。于是,我在我的版本中进行了筛选。这个方法出奇地有效!

接下来,我更新了我的初始提示,增加了更多智能设备的控制,减少了不必要的实体,增加了对脚本的支持,并且尽量避免系统在未被明确请求的情况下执行操作。经过多次尝试,我终于得到了一个几乎完美的解决方案(尽管由于我的 4060Ti 显卡的内存带宽限制,运行速度有些慢)。以下是最终的成果:

❓ 常见问题解答(FAQ)
如何用本地大模型做智能家居语音助手?

核心是把本地 LLM 接入 Home Assistant,再通过提示词定义助手角色、语气和控制规则。这样可在本地完成语音理解、意图判断与设备控制,减少对云端服务的依赖,更适合重视隐私和稳定性的场景。

这篇文章提供了可直接用的提示词模板吗?

有。正文摘录中包含了用于拼接 system/user/assistant 消息的模板结构,并定义了 GlaDOS 风格的响应要求。它更像是一个可改造的提示词骨架,便于按自己的智能家居环境继续调整。

本地化 LLM 智能家居方案最大的价值是什么?

最大价值是隐私与可控性:语音和控制逻辑尽量留在本地,减少外部平台依赖。同时还能通过角色提示词塑造交互风格,让助手更符合个人偏好,而不是千篇一律的通用回答。

🔬 语宙深潜追问 · 进阶实操拆解
本地语音助手如何降低延迟?

优先把唤醒词、ASR、意图识别和控制指令拆成轻量链路,常驻小模型做前置判断;大模型只处理复杂意图。再配合流式输出、缓存常用指令和局域网直连 Home Assistant,延迟会明显下降。

角色化提示词怎样避免误控家居?

把系统提示词写成“权限分层+动作白名单+确认机制”。对开灯、调温这类低风险动作可直接执行;涉及门锁、安防、夜间模式等高风险操作,必须二次确认,并在提示词中明确拒绝越权指令。

🗳️ 读者观点微投票 · 您的实战立场是?
本地LLM语音助手,最该优先牺牲什么?
🕸️ 语宙向量知识图谱 · 语义强关联深度内链
🐋 所属权威专题:DeepSeek 深度实战与部署 →
  • Soundwave – 港中文深圳开源的语音理解大模型
  • Voila – 开源端到端语音大模型,实现低延迟语音对话
  • Step-Audio-AQAA:突破ASR/TTS瓶颈!StepFun推出端到端音频语言模型,重塑人机语音交互
  • LM Studio – 开源、傻瓜、一站式部署本地大模型 (LLM) 的应用平台
🏛️ 宝玉的分享 · 前沿大模型翻译与提示词工程实战分享专栏,聚焦海外一手 AI 技术动态与工程实践。
📄 Markdown 纯净版
💡 这篇内容对您有启发吗?
📡 RSS 订阅✨ 提交 AI 工具 / 合作
🚀 Prompt 语宙 AI 创作者生态:探索 2,800+ 全球实用 AI 工具与高精度生图提示词咒语库
🧭 语宙 AI 导航 (ai.paooo.com)🎨 AI 生图 Prompt 库📚 核心专题导航⚡ AIGC 早报生成器
Nemotron-Labs-TwoTower – 英伟达开源的双塔架构扩散语言模型
ProPainter – 南洋理工大学推出的AI视频修复项目
QwQ-32B-Preview – 阿里开源的AI推理模型,基准测试超越 o1 模型
别再数Token了:OpenAI甩出AI时代记分卡,用”有用智能每美元”给CFO算清ROI
Pneuma
TAGGED:AI智能体AI音频与语音Llama大模型微调开源大模型
分享
Email 复制链接 打印
Share
宝玉的分享 头像
By宝玉的分享
Follow:
前沿大模型翻译与提示词工程实战分享专栏,聚焦海外一手 AI 技术动态与工程实践。
上一篇 Snowflake 数据云的图片 技术领导者需要知道的 5 个关于生成式 AI 的残酷真相 [译]
下一篇 科学与工程助力更优秀的文本生成 [译] 科学与工程助力更优秀的文本生成 [译]
Ad image
Ad image

最近更新

WordPress 7.2版本更新与默认随机重定向、Secrets API撤回及MCP核心能力拆解封面图
官方博客竟把关闭过滤器写错了!WordPress 7.2前瞻全拆解:默认/random/暗藏隐私与SEO风险、Secrets API紧急撤回与3项MCP只读能力落地
AI 工具
Anthropic上市募资与算力长约的隐喻:现金光环上升,数据中心暗链延伸,治理水晶承受张力与阻力冲击。
募资超1070亿美元却背负9000亿算力长约!Anthropic史上最大IPO背后的三大隐忧:1040亿年内亏损、地方抵制潮与PBC治理死结
AIGC 资讯
微软Copilot与Claude/ChatGPT价格战隐喻:发光玻璃表格堡垒守住Excel,数据流高效汇聚,企业AI竞争升级
3000万付费仅吃下4.5亿席位不到7%!微软Ignite正面叫板Claude与ChatGPT:月均30美元VS 205美元价格战与Excel保卫战全拆解
AIGC 资讯
联想AI推理时代的端边云全栈算力插画:玻璃拟态服务器核心发光,光流连接云端与边缘节点,呈现营收与订单增长动能。
AI营收暴涨80%且握5300亿服务器订单!联想Q2单季营收首破2000亿、净利狂飙166%:端边云全栈算力如何接住推理时代红利?
AIGC 资讯

相关推荐

FlashFace – 阿里联合香港大学推出的高保真AI写真工具
AIGC 资讯

FlashFace – 阿里联合香港大学推出的高保真AI写真工具

Prompt 语宙研究院
3D与空间智能 AI绘画提示词 开源大模型
ActAnywhere – Adobe推出的AI视频背景生成模型
AIGC 资讯

ActAnywhere – Adobe推出的AI视频背景生成模型

Prompt 语宙研究院
3D与空间智能 Adobe AI智能体 AI视频生成 大模型微调
Seed1.6:字节跳动MoE模型新突破,256K长上下文推理引领多模态新范式
AI 工具AIGC 资讯

Seed1.6:字节跳动MoE模型新突破,256K长上下文推理引领多模态新范式

Prompt 语宙研究院
AI办公效率 AI智能体 MoE架构 Seed1.6 多模态 字节跳动 豆包大模型
llmware – 专为企业级应用设计的开源统一框架
AIGC 资讯

llmware – 专为企业级应用设计的开源统一框架

Prompt 语宙研究院
AI智能体 RAG检索增强 大模型微调 开源大模型
/ Prompt 语宙 /

探索生成式 AI 的无限创作潜能,一站式获取前沿 AIGC 资讯、高阶 Prompt 咒语与全球实用 AI 工具。

核心专栏

  • 语宙 AI 工具导航
  • EVA 视觉抠图工坊Hot
  • 出海数字营销宝典
  • AI 生图咒语灵感库
  • 24H 硅谷 AI 情报流

生态与服务

  • 语宙 AI 导航
  • 全部资讯
  • AI 生图咒语库
  • AIGC 早报生成器
  • 核心专题
  • 提交工具 / 合作

标签

开源大模型 AI智能体 AI办公效率 AI绘画提示词 OpenAI 大模型微调 Midjourney AI编程 stable diffusion AI视频生成 ChatGPT 3D与空间智能 HuggingFace AI音频与语音 RAG检索增强 Claude Flux AIGC Gemini 通义千问 Anthropic Llama Cursor DeepSeek Prompt AI Agent Kimi 智谱AI 具身智能 YouTube
Prompt 语宙Prompt 语宙
Follow US
© 2023–2026 Prompt 语宙 (paooo.com). HalfPX. All Rights Reserved.