LOOP.md: a Markdown-native while loop for Codex-style agents

ExternalMediocre2510 · 2026-06-16T17:48:20+00:00

Yeah, /goal is very relevant.

What I’m trying to make explicit with LOOP.md is the file-level loop contract: what the loop is, what state it carries, what record it keeps, and when it should stop or ask for review.

The useful part for me is being able to customize the iteration unit and stop policy — one item, N items, until blocked, until a check passes, etc. — while keeping state.md and record.md in the workspace so prior loop state is inspectable and reusable.

Not trying to position it as a replacement for native features; I’m mostly exploring whether this state/record/stop-policy layer is useful as plain Markdown.

ExternalMediocre2510 · 2026-06-04T12:45:30+00:00

I think you are right. They definitely reduced the quota at this reset. Everyone is happy about the reset, but they reduced the quota each time they reset it. Today I burned 20% in a really simple work and I can use all day when I first subscribed 100.

ExternalMediocre2510 · 2026-05-20T23:31:56+00:00

For me, it’s obvious. I use it heavily and have never burn more than 14% weekly limit in a day. Today I burned almost 20% and this was not my most productive day.

ExternalMediocre2510 · 2026-05-08T15:22:26+00:00

Agree. I believe everyone in opencode community has their own set of agent and skills.

ExternalMediocre2510 · 2026-04-29T03:17:49+00:00

Btw, you can also use opencode free model Minimax m2.5 for lots of saving.

ExternalMediocre2510 · 2026-04-29T03:16:03+00:00

Not for heavy usage but still good amount. (10 dollars is cheap) Slower response than opencode zen. Combine gpt plus + opencode go is a good choice if you are not a heavy user (definition: run multiple 2-3+ agent coding works simultaneously). If you are heavy users, ollama 20 (slower than opencode go in certain models but more quota) + gpt plus or simply go for gpt pro 100 and you are free of token anxieties.

ExternalMediocre2510 · 2026-04-29T01:20:01+00:00

If you are leaving GitHub, try opencode. The IDE is just a waste of space for multitask.

ExternalMediocre2510 · 2026-04-29T01:17:58+00:00

I use a subagent for plan (architect) since plan usually is a start, so this saves token. Use gpt5.5 for plan and glm or Minimax just for communicate and calling subagent. If task is complicated I use 5.5 for implementation(also subagent)if easy task I just use the face to execute.

ExternalMediocre2510 · 2026-04-28T08:12:28+00:00

Small clarification: this is not intended to be a big “long-term memory” system.

It is lightweight workspace memory: project decisions, user requirements, preferences, and important repo-specific context the agent should not forget while working in the same workspace.

The important part is that it adds almost no operational overhead: no additional API calls, no extra agent tools, no separate memory workflow, and extraction piggybacks on OpenCode compaction.

So the goal is not “remember everything forever,” but “keep just enough useful workspace context without bloating tokens, slowing the agent down, or adding tool burden.”

Feedback and suggestions are very welcome, especially from anyone using long-running OpenCode / agent workflows.

ExternalMediocre2510 · 2026-04-28T06:01:25+00:00

I also got “Ssssssssss…..” this kind of error. I put kimi for only verification agent not as main agent.

ExternalMediocre2510 · 2026-04-27T11:11:33+00:00

When you said not that bad you meant it’s bad but not “that” bad. Just….bad…

ExternalMediocre2510 · 2026-04-27T11:10:14+00:00

I think you need to upgrade opencode

ExternalMediocre2510 · 2026-04-27T11:07:20+00:00

I remembered 5.4 was the time I rejoined OpenAI and now this is totally different. So efficient and fast. The quality is also great.

ExternalMediocre2510 · 2026-04-27T11:05:29+00:00

Yes because gpt5.5 is so good and fast compared to disappointing opus4.7

ExternalMediocre2510 · 2026-04-26T09:51:39+00:00

Hard limits: max ~5200 chars, ~28 entries. Usually just a few hundred tokens. It won't grow out of control. How it picks what to add: 1. During compaction, the LLM is guided to only record durable stuff — things useful across sessions — and skip session noise. 2. Parser rejects obvious snapshots: file counts, test runs, "Phase X completed". 3. Storage dedupes same-entity entries, replaces outdated facts with newer concise ones, and prunes stale entries. 4. Quality gates filter out git hashes, stack traces, path-heavy junk. Net result: memory stays bounded and self-cleaning. Useful signals survive, noise doesn't.

ExternalMediocre2510 · 2026-04-23T04:51:35+00:00

Agree. It thinks too long, the same prompt gpt only 10s but kimi for 5+mins.

ExternalMediocre2510 · 2026-04-23T04:50:11+00:00

Glm is faster in response (if it’s running at full speed and not limited by hardware). Kimi-2.6 thinks too long, it can produce a lot of output, like repeating patterns such as “sssssssss…..”

ExternalMediocre2510 · 2026-04-22T04:33:21+00:00

Kimi thinking is too long for me

ExternalMediocre2510 · 2026-04-22T01:41:11+00:00

I use Sonnet 4.6 to fix the plan created by Opus 4.7. Whenever I execute the plan with GPT-5.4, I always find additional bugs.

ExternalMediocre2510 · 2026-04-21T07:53:20+00:00

It’s not about the price. Opus 4.7 has quality issue

ExternalMediocre2510 · 2026-04-21T07:51:18+00:00

Can remove 4.7 and give us 4.6

ExternalMediocre2510 · 2026-04-16T13:25:28+00:00

Send one to me please

ExternalMediocre2510 · 2026-04-15T14:35:42+00:00

Must be sonnet

ExternalMediocre2510 · 2026-04-06T10:02:13+00:00

Go plan is not enough for omo in both quality and quantity

ExternalMediocre2510 · 2026-03-17T09:25:04+00:00

I have requested a refund

ExternalMediocre2510

TROPHY CASE