Changelog
What changed, and what is coming next.
Written from the product’s history, newest first: 5 groups, 22 changes. Field is booking its first pilots, so these are changes to the product as built, not general availability.
- Web UI
- 5
- API
- 4
- Agents
- 5
- Security
- 3
- AI
- 1
- Platform
- 4
Coming next
Being built now.
No dates: each of these ships when it passes the same tests as everything below, and then moves into the list below. Some are rolling out to pilot customers first.
- IntegrationsServiceNow and Zendesk, both ways: reports become incidents or tickets with an evidence summary and a link back; status and replies come home.
- IntegrationsWebhooks and API keys you manage in your portal, for your own tools.
- FleetA cluster board across models, firmware, app versions and sites; regression watch that can pause a rollout; early capture when an issue spreads; health trends and a monthly savings report.
- AIEngineers confirm or correct the AI's root cause, and confirmed causes become known issues that fix the next report, with people still approving.
- RemoteRemote sessions as a last resort: view, control and a locked-down console, off by default, consented on the device, approved, blanked during payments, recorded and time-limited.
- AgentsSDKs for Android, React Native and iOS; deeper integration with a first terminal maker and hardware-backed device identity.
- AgentsAgent updates from your portal: a pilot group first, and version pinning per client.
A website that is finished, and a demo form that sends
Every page completed to the same standard, and the first public API endpoint.
- APIA public endpoint for Book a demo requests: validated, protected against spam and abuse, the visitor's IP never stored as is, and an audit row without personal data.
A new web UI: Briefing and Workbench
One design system and chart kit for the customer portal and the staff console.
- Web UIDesign foundation: a token layer with two skins, primitives, an SVG chart kit and a keyboard layer.
- Web UICustomer portal (Briefing): overview, devices, a report's case file, approvals, tickets, enrolment, policy, settings, SSO domains and the SAML signing key.
- Web UIStaff console (Workbench): the queue, reports, clusters, known issues and the Coder.
- Web UIFix buttons say what will happen: Run now, Ask for approval, or Blocked.
- APIFields the UI needs: each report's outcome kept by a trigger, device health, richer stats, list filters, device names on approvals.
Pilot hardening
The changes a bank's security team asks for first.
- SecurityApprovals are signed by a separate service, kept apart from the one that sends commands.
- SecuritySingle sign-on only for domains proved by a DNS record, re-checked daily; SAML requests signed with a per-organisation key.
- AgentsDesktop redaction from 0.7 to 16 MB/s with byte-identical output.
- AgentsDesktop transaction guard: the POS app's transaction signal, and an explicit setting for machines that never take payments.
- AgentsThe Android agent builds into a real APK (Android 7.0+, target SDK 35) with app tests, lint and release signing in CI.
- PlatformA demo dataset and screenshot script, with fixes found by looking at the screenshots.
A standalone platform: identity, tickets, the Coder
Field stops depending on other systems: it owns its people, organisations, tickets and code fixes.
- PlatformIdentity: users, organisations, roles, sessions, magic links, OIDC and SAML single sign-on, organisation administration and the staff API.
- PlatformField-owned tickets: numbering under concurrency, visibility per comment and attachment, notifications that never carry device content.
- AIThe Coder: code-level investigation at the commit a device runs, four-eyes approval of its plan, budgets, a sandboxed runner and draft pull requests only.
- AgentsBrowser agent: a Chrome extension for web POS and back-office portals, with a new browser.reload_tab playbook.
- Web UIThe first customer portal and staff console on the as-built API.
Foundations: protocol, gateway, agents
The signed device protocol, the redaction rules and the first agents in Kotlin and Go.
- PlatformA signed device protocol, shared redaction rules and the signed playbook library.
- APIThe service: enrolment, signed check-ins, reports checked again on the server, triage, policy, approvals and the tamper-evident ledger.
- SecurityThreat model, deployment files and CI.
- AgentsAndroid agent core and the Go desktop agent, byte-for-byte compatible with the reference; fail closed on an unreadable command time.
- APICustomer API: per-organisation origins, filtering reports by status.
Every entry is backed by a change in the TickFlow Field repository, which customers and assessors can review under NDA. Security fixes are listed once they are deployed; see the trust centre.