pixir

# Pixir Harness Open Beta Developer Preview

Date: 2026-06-09

Pixir Harness is ready for a small developer preview. This note records the initial
source-install beta stance; ADR 0025 later defines Hex as a narrow CLI/ACP distribution
path, not a stable Elixir library contract.

This is not a stable ecosystem release. The goal is to let early users install Pixir,
run `doctor`, try a first terminal or ACP-driven turn, and report the first
installation, auth, model, and workflow failures with useful evidence.

## What Is Supported

- Source install from `https://github.com/ranvier2d2/pixir-harness`.
- Hex escript installation when the `pixir` package is available, scoped to the same
  CLI/ACP runtime.
- Terminal CLI through the built `./pixir` escript.
- ChatGPT subscription login through `./pixir login`, with `OPENAI_API_KEY` as a fallback.
- Local append-only Session Logs under `.pixir/sessions/`.
- `./pixir doctor --json` as the first no-network diagnostic gate.
- ACP over stdio through `./pixir acp`.
- Agent Skills, Subagents, Workflows, Session tree inspection, and durable compaction
  checkpoints.
- Durable Provider usage accounting for token/cache evidence.
- Initial Image Attachment support through local Session Resources and Provider
  projection.
- Provider-hosted Web Search request/evidence plumbing, with opt-in smoke verification.

## What Is Experimental

- Long-running, non-blocking Subagent status and result retrieval.
- Workflow partial outcomes and checkpoint bundles as a product experience.
- T3Code integration through the separate local adapter/patch workflow.
- Networked smoke tests for model/provider behavior.
- Skill Context Hydration, which is accepted as a design direction but not yet a public
  implemented surface.

## What Is Out Of Scope For This Preview

- Stable public Elixir API.
- Broad package ecosystem or extension API promises.
- MCP server support.
- Packaged T3Code provider.
- Self-update/install channel.
- Production SLA, telemetry, or hosted service guarantees.

## Newcomer Smoke

The expected first-run proof is:

```bash
git clone https://github.com/ranvier2d2/pixir-harness.git
cd pixir-harness
mix deps.get
mix escript.build
./pixir doctor --json
```

A clean clone smoke on 2026-06-09 completed those steps and returned `ok: true`,
`status: "ready"`.

## Feedback To Capture

When a preview user reports a failure, ask for:

- exact OS and Elixir version;
- command run;
- `./pixir doctor --json` output with secrets removed;
- whether they used ChatGPT subscription login or `OPENAI_API_KEY`;
- the relevant `.pixir/sessions/<id>.ndjson` only when safe to share.