Log inGet started
What it does

source

The DotBot panel's data source — the one seam between the editor panel and the DotBot agent surface.

This implementation is a fixture. Every reading it hands back is a constant written into its init.luau. It talks to no plugin, no provider and no network, spends nothing, and holds no credential. It exists so the panel can be built and looked at while the real surface is built elsewhere.

The contract is shaped after the dotbot.* trusted exports, so swapping the fixture for the real surface is a change to this one file:

HalfMembers
Read-only, answered in the frameavailable, agents, agent, terminalAgents, accounts, accountsFooter, models, model, levelsFor, level, usage, conversations, currentConversation, history, sendable, events
Start / poll, because a trusted handler may not yieldconnect.start / .poll, openSignIn.start / .poll, disconnect.start / .poll, send.start / .poll
Read-write but unpricedsetModel, setReasoning, modelOf, levelOf, stop
The half only a fixture hasfixture.enable, fixture.scenario, fixture.approve, fixture.setConnected, fixture.dropEventsBefore, fixture.reset

A start answers { ok = true, id } or { ok = false, reason = "busy" }. A poll answers pending, awaitingPerson, done, refused or error. A device-code flow carries its code, its page and its expiry on the awaitingPerson answer, because that is what a person has to be shown while the job waits.

Two done answers carry a flag that says the fixture did not do the thing: openSignIn reports opened = false with the address it would have opened, and send reports delivered = false with the reason. The panel shows both rather than leaving a button that looks like it worked.

fixture.enable(false) takes the data away, and the panel says "DotBot is not available in this build" instead of drawing a conversation nobody had.

Scenarios

fixture.scenario(name) puts the readings into one state at a time: normal, fresh, notice, warning, blocked, signInExpired, codeExpired, codesUnavailable, notLinked.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

0items
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.