Nick Owens wrote:
> On Tue, Jun 30, 2026 at 6:55 PM Daniel Dickman <didickman@gmail.com> wrote:
>>
>>
>>
>> On Wed, 1 Jul 2026, David Uhden Collado wrote:
>>
>> Hi David, thanks for taking a look.
>>
>>> Are there any plans to port opencode to OpenBSD as well? From a maintenance
>>> perspective, it seems like one of the more useful candidates because it
>>> supports models from many different providers instead of being tied to a
>>> single vendor.
>>
>> No I have no plans, but there's nothing stopping someone that wants to
>> tackle it. As I'm sure you're aware there's some history between opencode
>> and crush.
> 
> there is absolutely something stopping someone from porting opencode.
> opencode depends on bun, and for reasons that only mac users and
> javascript programmers understand, bun depends on bun now to build.
> bun does not work on any of the BSDs, and the effort to do the freebsd
> port upstream prior to this situation got dropped. as far as i can
> tell there is no plan by upstream to fix this.

Fair point about opencode. I was thinking mostly about the maintenance 
angle: a provider-agnostic agent can reduce the need to maintain a 
separate CLI for every vendor.

But if opencode depends on Bun, and Bun is not usable on BSD, then I 
agree it is a bad ports target for now.

I also looked at some similar provider-agnostic tools. Cline is 
interesting, but its source tree has moved to Bun as the package 
manager/build tool. Kilo Code is similar: it has a CLI, but its 
development workflow also depends on Bun.

So I agree that crush and swival are much more realistic imports today. 
Crush being self-contained Go code and swival being mostly Python makes 
them a lot more suitable for the ports tree than this Bun-based tools.

> 
>>
>> crush supports many providers. (fire it up and the first prompt is to pick
>> your favourite provider). swival also supports many providers, but is a
>> more specialized agent.
>>
>> I have sent the ones that would be useful to me (codex is already in ports
>> and I use it too).
>>
>>>
>>> My concern is that importing many AI-agent CLIs could become expensive to
>>> maintain.
>>
>> I've put myself down as maintainer, I don't think it's very much burden to
>> be honest.
>>
>> claude will be frozen in time and can't be updated given the
>> discontinuation of the npm distribution.
>>
>> swival is mostly python which I can easily keep up with and crush is
>> self-contained go code.
>>
>