fix(opencode): pass missing auth headers in run --attach

[ericclemmons]

Issue for this PR

Closes #16096

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Adds missing Basic auth headers to run command, just like attach.

How did you verify your code works?

Relied on tests (that I've since removed to be consistent with the other patterns) and comparing run against opencode serve vs. one with Basic auth (like what OpenCode.app starts):

1. ✅ opencode --attach http://127.0.0.1:45103 --dir ~/workspace run howdy

2. ❌ OPENCODE_SERVER_USERNAME=opencode OPENCODE_SERVER_PASSWORD=hunter2 opencode --attach=localhost:4096 run howdy

   Error: Session not found

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

Notes

I originally started refactoring out a getAuthorizationHeader utility based on

opencode/packages/opencode/src/cli/cmd/tui/worker.ts

Line 147 in 85ff056

function getAuthorizationHeader(): string | undefined {

, but opted for inlining & duplicating what was in

opencode/packages/opencode/src/cli/cmd/tui/attach.ts

Lines 63 to 68 in 85ff056

	const headers = (() => {
	const password = args.password ?? process.env.OPENCODE_SERVER_PASSWORD
	if (!password) return undefined
	const auth = `Basic ${Buffer.from(`opencode:${password}`).toString("base64")}`
	return { Authorization: auth }
	})()

I did use AI to author this because I was in the middle of another project when I finally asked Claude "Wait, is this an opencode bug??" and wound up here.

I'm sorry. 😔

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found one potentially related PR:

feat(github-action): Support remote server connection via --attach (#15866)

• This PR also deals with the --attach functionality and remote server connections, which is related to the auth headers fix being addressed in PR fix(opencode): pass missing auth headers in run --attach #16097.

However, this appears to be a feature addition for GitHub Actions rather than a direct duplicate of the auth headers bug fix. The current PR (#16097) is specifically addressing a bug where auth headers are missing when using run --attach, while #15866 focuses on enabling remote server connection support in GitHub Actions.

No duplicate PRs found

[ericclemmons]

So that we're consistent with attach:

opencode/packages/opencode/src/cli/cmd/tui/attach.ts

Lines 37 to 41 in 85ff056

	.option("password", {
	alias: ["p"],
	type: "string",
	describe: "basic auth password (defaults to OPENCODE_SERVER_PASSWORD)",
	}),

[ericclemmons]

This is modeled after

opencode/packages/opencode/src/cli/cmd/tui/attach.ts

Lines 63 to 68 in 85ff056

	const headers = (() => {
	const password = args.password ?? process.env.OPENCODE_SERVER_PASSWORD
	if (!password) return undefined
	const auth = `Basic ${Buffer.from(`opencode:${password}`).toString("base64")}`
	return { Authorization: auth }
	})()

[nexxeln]

This still hardcodes "opencode", so run --attach will keep failing against servers using a non-default OPENCODE_SERVER_USERNAME. Can we read the username from env here (like worker.ts) instead of only fixing the password path?