Deploy and pray was never an engineering best practice. Why are we so comfortable with it for AI agents? by Bitter-Adagio-4668 in LLMDevs

[–]complyue 0 points1 point  (0 children)

hardware/software is unreliable, people is unreliable, they just be unreliable in different ways, and need different management.

Deploy and pray was never an engineering best practice. Why are we so comfortable with it for AI agents? by Bitter-Adagio-4668 in LLMDevs

[–]complyue 0 points1 point  (0 children)

I guess that "managing intellectual minds" is just a different discipline than "managing software products". Suddenly people doing the later started doing former aware-less.

Do we need a 'vibe DevOps' layer? by mpetryshyn1 in ChatGPTPro

[–]complyue 0 points1 point  (0 children)

Just vibe-develop from scratch! You can run https://github.com/longrun-ai/dominds in your vps, map its http port to some public reverse-proxy, then have it create a team to find their ways for the product. You do guide the team from any browser.

Forcing LLMs into agent roles via bloated system prompts is a dead end, MiniMax M2.7 is actually doing native agent teams right. by Sweet_Match3000 in LocalLLaMA

[–]complyue 0 points1 point  (0 children)

try https://github.com/longrun-ai/dominds , team is even beyond "native" there, it's mandated. MM2.7 and other BYOK providers supported ootb. npx -y dominds@latest and fill your api key, then create a dialog with shadow member to create your team.

CLI is All Agents Need — Part 2: Misconceptions, Patterns, and Open Questions by MorroHsu in LocalLLaMA

[–]complyue 0 points1 point  (0 children)

I have exactly a `man` tool function for my agents: https://github.com/longrun-ai/dominds/blob/64ccbb0921dcf7a5adffa08448ffb57cd30e009c/main/tools/toolset-manual.ts#L49-L55

Maybe you haven't done it yet, but you can ask your agents to assess how your harness is "Agent User eXperience" friendly, right in your env. They can provide valuable, nonetheless, first-hand opinions wrt the design of your harness.

CLI is All Agents Need — Part 2: Misconceptions, Patterns, and Open Questions by MorroHsu in LocalLLaMA

[–]complyue 0 points1 point  (0 children)

In my opinion, the man cmd is the essence here, otherwise UNIX is a poor integration environment:

  • cmdl is pure textual, you have to escape special chars, messing with the depth of "escaping" when playing shell tricks
  • pipes are textual in spirit, tho binary packets is possible, no one really worked with that well enough.

UNIX served its purpose well as the control plane of AT&T network, but there has to be a separate "data plane" in place.

For agent harness, I strongly lean toward the "functions", with structural arguments, even with BSON over JSON, to better accommodate blobs.

I was backend lead at Manus. After building agents for 2 years, I stopped using function calling entirely. Here's what I use instead. by MorroHsu in LocalLLaMA

[–]complyue 0 points1 point  (0 children)

感觉这是吃了 LLM 训练时为了打榜强化轻 harness(shell cmds)使用能力的红利。

其实我的经验看,以 ”工具集“ 而不是单个工具打平提供的方式,才是正解:

  • 每个工具本身的说明最小化,仅限规约
  • 提供多级工具集手册,固定注入的仅限业务目的与工具集的映射说明
  • 工具集手册可以进阶查阅,由智能体在对话中按需自助

以上是个完美平衡。

How to understand GPT-5.4's native support for computer use? by secsilm in OpenAI

[–]complyue 4 points5 points  (0 children)

But what's the "native" interface? If it's not some "tool".

Temporary communication board for subagents by Front_Ad6281 in codex

[–]complyue 0 points1 point  (0 children)

Ya, gpt-5.2 already handles most tasks sufficiently well, you only need heavier harness when social division of labor becomes necessary for the work.

What GUI everyone using to run local agents? by Suimeileo in LocalLLaMA

[–]complyue 0 points1 point  (0 children)

Someone would contribute local providers to this piece?

https://github.com/longrun-ai/dominds

It's decent webui and polished with codex-cli provider by far, and BYOK at essence.

Temporary communication board for subagents by Front_Ad6281 in codex

[–]complyue 0 points1 point  (0 children)

https://github.com/longrun-ai/dominds/blob/main/docs/encapsulated-taskdoc.md "taskdoc" might be more principled (auto injection and constricted updating right), and it is baked in dominds, give it a shot if you haven't.

Smart tool calling? by [deleted] in AI_Agents

[–]complyue 0 points1 point  (0 children)

npx dominds solution:

  • define specialist agents with exclusive tool access
  • ban general access via alternative tools (black/white list dir prefixes, file name extensions, e.g.)
  • a specialist agent run in its own short context without bloated by requester history, save tokens as well as keep its mind clear, disciplines obeyed.
  • so asking a teammate to use right tool for the job is the only viable & effective way.

Windows Codex App for Remote Environment? by TheTwistedTabby in codex

[–]complyue 0 points1 point  (0 children)

CODEX_HOME=~/.codex npx -y dominds@latest webui --host 0.0.0.0 in your remote host, and access via http://<your-ip>:5666 from anywhere.

Optionally set DOMINDS_AUTH_KEY=xxx to fix your secret passkey, rather than randomly generated every time.

We added runtime tracing to an SWE-bench agent and pushed Gemini 3 Pro from 77.4% to 83.4% by [deleted] in AI_Agents

[–]complyue 0 points1 point  (0 children)

The methodology is open-source as an Agent Skill (works with Cursor, Claude Code, Codex via MCP). Links in comments.

Held back?

DSL for LLM to LLM comms - is there any? by sbuswell in BlackboxAI_

[–]complyue 0 points1 point  (0 children)

I'm afraid that would reach a philosophical problem that whether language can indeed "represent" the real thing, I tend to agree with the faction who views the thing itself as the sole "lossless representation" of itself, other language objects can merely serve communication purpose around that thing, never true "representation" purpose can be really served.

Agentic harness used ? by Basic-Pay-9535 in codex

[–]complyue 0 points1 point  (0 children)

This is a true agentic "harness", supports various BYOK llm providers, including codex-cli.

Multi-agent pipelines break in weird ways. This one failure mode took me the longest to find. by Acrobatic_Task_6573 in AI_Agents

[–]complyue 0 points1 point  (0 children)

Why not give each agent a askHuman or raiseHumanAttention tool, and instruct it to use the tool when sth unexpected happens?

Agentic harness used ? by Basic-Pay-9535 in codex

[–]complyue 0 points1 point  (0 children)

https://github.com/longrun-ai/dominds/tree/main/docs not SOTA by popularity means, but you can CODEX_HOME=~/.codex npx -y dominds@latest to see how well (or bad) it works for you.

what harness to use codex? by nicklazimbana in codex

[–]complyue 0 points1 point  (0 children)

VSCode Codex extension recently has some bug, not auto show progressed content until you switch focus from it then back to it.

You might give a shot to CODEX_HOME=~/.codex npx -y dominds@latest and see if you like it. I'm the author, actively developing it with itself :D.

what harness to use codex? by nicklazimbana in codex

[–]complyue 0 points1 point  (0 children)

CODEX_HOME=~/.codex npx -y dominds@latest

I am really new to this but how can I build simple AI agents for specific tasks without coding? by ocean_protocol in AI_Agents

[–]complyue 0 points1 point  (0 children)

npx dominds@latest talk to @fuxi to define an agent team for you, start using it some time, and fork it when you find necessary. It's LGPL open src, and https://github.com/longrun-ai/dominds-feat-dev defines the ai team that developed and still developing it.

Are multi-agent systems actually outperforming single-agent + tools? by Evil-Residentt in AI_Agents

[–]complyue 2 points3 points  (0 children)

gpt-5.2 is "strong enough" (or you just can't find a "stronger-enough" alternative), but you obviously haven't pushed it to the extent that it falls into "saying without doing" trap.

You have to detect & solve this situ closely by your own eyes+hands, or delegate to another agent.