[meta] Hero Sandbox Review #275
Labels
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#275
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rolling review of the Hero OS sandbox by the whole team. Post findings as comments, ideally one finding per comment with a screenshot.
How to read this issue
Original capture (2026-06-09, kept for history)
Cockpit/Deployer
would be good then we have the terminal available
NOTE: For now we do 1 slice = 4gb and 1 tester vm =2xslice, otherwise we have 1 tester vm = 1vcpu, 4gb, would be too slow
Cockpit/Deployer
Admin page
Deployer/Cockpit
we need spaces on the control buttons or more room
Cockpit/Deployer
these need to be a toggle button
Cockpit/Deployer
also need an option to upgrade all services
Kimi Agent
even after an upgrade it does not work
but sometimes kimi agent works after a while. need to investigate
hint: check if its an issue with kimi itself or when it is in the deployer
Deployer
Deployer/Cockpit
also on the whiteboard + the rest of the services all need to have voice integration
Hero_voice
the hero voice quality seems to be not that great?
hero_planner
doesn't get filteredactually even selecting any of these pins doesn't do an filtering tooFixed
Deployer
Tried deleting one of my VMs since I deployed two. Hit this
And this if I hit "install"
Hint: maybe it was due to restarting the admin deployer at the same time. Seemed transient as hinted. considered fixed.
Hero cockpit/deployer
FIXED
hero_db_admin
upgrading cockpit
herobiz
wrong theme

a vm install
Hero Sandbox Features to Addto Hero Sandbox Reviewaccessing /admin/users
orchestrator launching kimi fleet
orchestrator by default not auth, no way to setup auth
also this is the admin page, but it still highlights agents tab
orchestrator fleet info don't exist (e.g what was the prompt, what were the repos,.. etc)
Apps descriptions (kimi, orchestrator)
slides claims to create dir if doesn't exist

Also, the buttons look disabled

The voice bar doesn't do anything

Also, these options go nowhere

buttons look disabled

pdf view
Try to record a question in books
can't install hero agent
Click "Huddle" at the top right

can't install Office
@AhmedHanafy725 wrote in #275 (comment):
On it
@AhmedHanafy725 wrote in #275 (comment):
I am removing hero_agent from the Sandbox for now, since hero_kimi is very good, and hero_orchestrator too. We don't need hero_agent for now and maybe never going forward, especialyl since Thabet is doing a lot of work on hero_shrimp and it's going well. So we can consider this done.
@thabeta wrote in #275 (comment):
Don't know by who, but this seems done. Good.
@AhmedHanafy725 wrote in #275 (comment):
That's a tricky one. Hero books needs aibroker, but I am not sure if we have aibroker working these days. @thabeta Any insights?
Hero Memory's UI is slow. Also, check the scroll bar
hero_biz feedback:
is loading between each tab necessary, makes it feel choppy and slow. can we lazy load instead? or perhaps fix underlying issue, api shouldnt be as slow.
when creating company (or any object) i get this error: Failed to save company: Internal error: Failed to save company: Network error: builder error
@thabeta wrote in #275 (comment):
Resolved in the current orchestrator build (integration). The fleet detail page now shows the prompt, the backend / model / effort / tools badges, the concurrency and repo count, and a per-repo card for every repo in the fleet. Minor polish still on the list (a collapsed full repo-path list + the created-at timestamp), but the core info is there.
@thabeta wrote in #275 (comment):
The tab-highlight half of this is resolved in the current build (verified live): the Admin page now correctly highlights the Admin tab, not Agents.
The other half — "orchestrator by default not auth, no way to setup auth" — is still open and tracked separately.
Status recap, 2026-06-12
Full pass over every finding in this thread, with current status. Legend: DONE shipped and verified, PARTIAL part of it shipped, OPEN not started or still failing, UNCLEAR needs a restatement or a retest to judge.
Big picture first: both onboarding paths were proven end to end today on a fully refreshed latest-integration channel. A brand new account and an existing account each went create, provision, install, browser SSO login, welcome email, working cockpit. RuyMaldonado, joriss, thabeta and timur all have fresh machines again (new web addresses, sent to each of you by welcome email). All release assets on the latest-integration channel were rebuilt and fresh installs were verified byte identical to the published binaries.
Platform: deployer and cockpit
AI assistants
Voice
App polish
Infrastructure note
The rented mainnet node turned out to be a newer light generation machine that only accepts the light workload family, while our stack deploys the classic workload types, so it rejects every deployment. Details and a placement guard proposal in hero_os_tfgrid_deployer#25. Until that is resolved all testers run on the QA node, which is nearly full (room for one more tester). A capacity decision is needed before the next wave.
If a row of yours says UNCLEAR, a one line restatement (or a quick retest on your fresh machine) is the fastest way to get it moving.
Hero Sandbox Reviewto [meta] Hero Sandbox ReviewTried to access the collab app on the running sandbox and i faced this error:
https://thabeta005k.gent01.qa.grid.tf/hero_collab/web/
Hero AIBroker keep loading models
Hero Foundry backend not found
hero_biz network err
new contact -> save redirects to edit contact with this following err
same err with adding new employee, new project ... almost adding any new thing
hero_docs download pdf produces err

hero_books read button not working

hero slides wizard failure

@AhmedHanafy725 wrote in #275 (comment):
This is not a collab bug, it is a deployment issue (livekit is not configured or run on the server)
hero voice

@thabeta wrote in #275 (comment):
Backend down ? Can't see the logs from router dashboard