http://127.0.0.1:8082, but not always. On a PC where more than one person has a Windows account, whoever opens Zeno second gets the next free port — 8083, then 8084 — because a port belongs to the machine rather than to the person signed in. The shortcut and the tray icon always know which one is yours.
While the console is running there’s a Zeno icon in the notification area. Double-click it to open the page; right-click it to stop the console. On Windows 11 a new icon starts hidden behind the ^ chevron at the left of the clock — drag it onto the taskbar to keep it in sight.
It reads the same local file the tools write to, so it’s current whether or not a chat client is running.
Finishing company setup
Setup Center is the landing page on a new install. It shows five checks for every registered company: exact file identity, permission, access choice, mirror coverage, and a harmless end-to-end test. Use Open in QuickBooks to launch the registered file, then Copy next step to send the exact unfinished action to your chat client. The console never opens a QuickBooks session itself; it coaches the permission dialog while the MCP connection does the check. After setup, Useful next steps reflects the install’s actual state. It can surface a stale mirror, a reviewed plan that was never applied, draft knowledge or playbooks, missing coding rules, and read-only questions worth asking. Copying a request doesn’t execute it.Picking a company
The sidebar has a company picker, and it scopes every page that’s about one client’s books. All companies shows everything this workstation has done. Every page has its own address, and the address carries the company:/knowledge?company=Ridgeline%20Properties%20LLC. Send a partner the link rather than a sequence of clicks.
Reviewing a plan
Plans is the landing page. Pending plans are listed with the company, who prepared each one, when, how many entries, and how many are blocked. Applied plans are hidden by default; tick Show plans that were already applied to see them. Open a plan to get every entry as a row: line number, date, type, name, amount, coding, reference, and the verdict planning reached — ready, worth checking, blocked, already posted. Against each line, record Include or Exclude. Put your name in the reviewer field and save the table in one go.Excluding a line records a decision; it doesn’t perform one.
qb_apply_batch reads those decisions when the agent runs it, skips what you excluded, and names the exclusions and who made them in its result.Runs
Every run, most recent first, with the company, what the batch was, who approved it, and how many entries posted or failed. Click a run for its entries — line number, type, date, name, amount, reference, status, and the QuickBooks transaction id each became. Failed entries carry QuickBooks’ own message. Reversals appear in the list like any other run, marked as reversals and linked to the run they undo. To undo a run, ask the agent:Work log
What was done and why, filtered by company and by period. Add entries here directly — the log is a record for people, and a person can write in it as well as the agent can. Entries the server generated for a session that ended without logging are labelled as machine-written. Treat one as a prompt to write the real entry.Knowledge, playbooks, and coding rules
The three things the agent has been taught, each readable and editable by the person whose judgement they encode. See what it remembers for what belongs in each. Knowledge — notes about a client’s books, grouped by category, with the vendors and customers each is anchored to. Drafts are marked. Confirm is what makes an entry start surfacing on its own during work; until then it does nothing. Playbooks — written procedures, with their slots and when to run them. Also drafts until confirmed, and a draft can’t be run. Coding rules — what each matches, what it fills in, whether it’s an auto rule or a suggestion, how many times it’s been used, and when it last applied. Move a rule between Auto and Suggest, or Forget it, which stops it applying and changes nothing already posted.Company files, status, and licence
Setup Center tracks authorization and mirror progress for each file. Company files lists what this workstation has registered — see several company files. Status describes this install: version, whether writing is enabled, where the run journal lives, this machine’s licensing id, and the name QuickBooks shows for it in Edit → Preferences → Integrated Applications. Licence shows your licence state, who it’s issued to, when its update window ends, your batch limit, and — on an unlicensed install — how many of your 250 transaction postings you’ve used. Paste a key and click Save key. Restart the connection in your chat client afterwards — the licence is read once, when the server starts. The same page shows this machine’s id, which support needs to move a seat to another workstation.What it can and can’t change
The console never writes to QuickBooks. Nothing on this page reaches a company file. What it does change is local: plan decisions, knowledge, playbooks, coding rules, work-log entries, and the licence key. It listens on127.0.0.1 only, so nothing on your network can reach it. Requests claiming to come from another host are refused, and a web page you happen to have open can’t read from it or post to it.
On a workstation two people share
Loopback is shared by everyone signed in to the PC, so127.0.0.1:8082 is not private on its own. Each Windows account therefore gets its own console: its own port, and a token created for that account which the page has to present. A browser belonging to anyone else is refused with a page saying so, rather than shown someone else’s clients.
This matters most on a workstation with fast user switching, where a colleague’s session keeps running in the background after they switch away. Their console keeps its port; yours opens beside it.