0.10.0: write a listing with an agent
Write a listing with an agent
An employer with a brief and no time can have a model expand it into the post form. Set OPENAI_API_KEY or ANTHROPIC_API_KEY and the box appears on /post; set neither and it does not.
It fills the form and stops. Nothing is written, nothing is published, and the person who asked reads and edits every field before a listing exists. That is the same seam an employer's agent goes through when it posts over the API and lands a draft, which is the board's thesis rather than a feature bolted onto it.
It will not invent compensation. If the brief says nothing about pay, every salary field comes back empty: an employer may not notice an invented range, and a candidate who applies because of a number nobody agreed to has been misled by this board. "Unpaid" has to be stated rather than inferred from silence, and it arrives as the checkbox 0.9.0 added.
Anything the model returns is checked against the same lists the form's own selects are built from, and an unrecognised value is dropped rather than bent into the nearest legal one, which would look like the employer chose it.
Two providers, because this is MIT software other people self-host and a board that only works if you bank with one vendor is not self-hostable. WRITER_MODEL overrides the per-provider default (gpt-5.2 / claude-opus-5). Written against both REST APIs directly rather than either vendor SDK.
Not a public text generator. Drafting needs an account and is capped at ten an hour per account, recorded before the model is called rather than after, since a request that failed still cost the board something. The provider's own error text never reaches the page.
OPENAI_API_KEY=sk-... # or ANTHROPIC_API_KEY=sk-ant-...
WRITER_MODEL=gpt-5.2-codex # optionalFull changelog: v0.9.0...v0.10.0