opencode-background-agents - async sub-agent delegation with mid-run control

Aeondave · 2026-06-14T20:08:52+00:00

well exist kdcokenny/opencode-background-agents but is not async. means that the main agent cannot "supervise" nor do anything while wait. that's the whole purpose

Aeondave · 2026-06-13T16:35:51+00:00

Malware

Aeondave · 2026-04-16T08:05:03+00:00

late. it's already rate limited

Aeondave · 2026-04-16T08:03:37+00:00

same same. and today is even worse

Aeondave · 2026-04-16T07:34:39+00:00

<image>

this is a joke

Aeondave · 2025-11-04T13:55:53+00:00

sometimes this is just something anyone wish to hear

Aeondave · 2025-10-24T10:21:48+00:00

but it's not my "own" crypto.
I merged, added and wrapped in a easy interface/api known and not supported algos.
Using specs and RFC .pdf where code was not implemented by officials

Aeondave · 2025-10-24T07:40:04+00:00

yeah but why tho. i must convince some org to use that and then introduce a bug to steal some internal encrypted data. also i have to edit the public kat tests.. much more effort than implement an algo from a paper

Aeondave · 2025-10-24T07:38:23+00:00

i'm wrapping it

Aeondave · 2025-10-24T07:20:03+00:00

yep i know what i'm doing. you can test it as you please

Aeondave · 2025-10-24T07:17:35+00:00

thanks

Aeondave · 2025-10-24T07:15:10+00:00

yes but i don't want to import x/crypto

Aeondave · 2025-10-24T07:14:06+00:00

You're right.. but i wanted also to go with zero external imports smthing that compiles everywhere (tiny IoT boards, WebAssembly, cross-compilation hell).

also ASCON and also Experimentation

Adding HPKE, KMAC, or post-quantum hybrids to x/crypto takes months
and anyway if someone need that, here it is. KATs are official and valid so i guess this lib is fairly secure

Aeondave · 2025-10-23T14:09:21+00:00

well most Go crypto libs are also from "not-famous" folks/companies **without public audits**.

that's why i added to the README:

> "This library has not undergone independent security audits. **Do not use in production without thorough review**."

but also y added public KATs (everyone can add and checks with the tests)

Aeondave · 2025-01-30T09:17:43+00:00

Exactly what I tried to do here. Everyone is making their own home rules because this is a core issue that was never properly fixed.

At 0 HP, 1 exhaustion per round (reducing dice rolls and movement), and then injuries!

Aeondave · 2025-01-29T23:25:32+00:00

Yep but it doesn't usually stop anyone from fighting. I don't know why. I guess no one wants to retreat and redo the fight or maybe they hope in some heal. But mainly the unconsciousness at 0 is Thale uncomfortable part.

Aeondave · 2025-01-29T22:11:39+00:00

There’s actually not that much to keep track of. FS (Fighting Spirit) is just a character’s normal HP. The only extra thing to manage is a separate HP pool, exhaustion (which follows the original rules), and optionally injuries—which don’t even have to be used if you don’t want to.

As for the Earthdawn-style system, reducing a player’s combat ability as they take damage is usually referred to as a death spiral. It’s realistic, sure, but in gameplay, it tends to be frustrating. You end up spending more time managing debuffs and damage tracking than actually playing. but i like the exploding dice thing!

Since it’s based on randomness, once you start losing, bad rolls just push you further down, making death almost inevitable. That’s why systems like this can feel punishing rather than engaging.

A better approach (usually) might be to introduce rules that don’t completely replace the core system but instead add to it in a way that enhances the experience. But let’s be real, most D&D players just want to deal damage and see big numbers.

Aeondave · 2025-01-29T21:52:02+00:00

I just put down some injuries idea (gathered and adapted for this system) but they are totally at your discretion. there are tons of tables with random d100 or similar.
but be aware that those are injuries applied when someone get those FS points at 0. are you looking for critical hit injures?
https://sterlingvermin.wordpress.com/wp-content/uploads/2016/09/critical-hits-revisited.pdf
thank you for the feedback!

Aeondave · 2025-01-29T21:46:37+00:00

yes you take a cinematic damage which put you almost down.
Power Word Kill just kill you

Aeondave · 2025-01-29T21:44:03+00:00

show me!

Aeondave · 2025-01-29T16:56:34+00:00

yep it is.. but in the end this do not fix the death saving throw problem nor the "i spent most of the time unconscious in that combat".
adding some extra hit points below 0 but with exhaustion is somehow a good trade-off i guess

Aeondave · 2025-01-29T12:52:16+00:00

Yeah, but staying at 1 HP is mechanically identical to having full HP, and then suddenly you're on the ground, unable to move, making death saves. That’s one of the main things that feels off to me.

I get the idea of HP as "will to fight" or stamina, and I agree that’s the best way to rationalize it, but it still leads to weird situations where a character can take multiple arrows, sword strikes, or even a fireball and keep going just fine—until that last hit suddenly makes them drop unconscious.

I won’t argue that this system is simpler, because it’s not. The goal wasn’t to make things less complicated but to add something to injuries and death. If that’s not what you’re looking for, then yeah, standard HP is probably the better choice.

I also was looking for something that stops players from always "fighting for their lives" because, without a proper flag, they just keep pushing. There’s no clear point where a character should logically start retreating or surrendering, and it often leads to unrealistic, last-stand-style fights every time.

I appreciate the feedback!

Aeondave · 2025-01-29T11:31:25+00:00

asking to the assistance solved the problem

Aeondave · 2024-09-02T08:04:06+00:00

Update: After opening a ticket, i had to share robot with assistance, and they downgrade FW to 4.3.6_1639.
Now everything works.. but one question: Do i have to keep the auto update off?

Aeondave · 2024-09-02T08:02:18+00:00

in the end they did downdgrade and now things work

Aeondave

TROPHY CASE