Skip to content

feat: update selkies web client build process and add no-sidebar diagnosis documentation - #46

Merged
gitricko merged 1 commit into
mainfrom
webtop-improvements
Aug 23, 2026
Merged

gitricko merged 1 commit into
mainfrom
webtop-improvements

Conversation

@intricko

@intricko intricko commented Aug 23, 2026

Copy link
Copy Markdown
Collaborator

This pull request addresses the most common failure mode in the Selkies webtop skill: serving the wrong web client (bare selkies-web-core instead of the full selkies-dashboard UI). It updates the documentation, scripts, and templates to ensure the correct build and deployment of the web client, improves error-proofing for autostart shell hooks, and adds a reference guide for diagnosing missing sidebar issues.

Web client build and deployment fixes:

  • The cmd_build_web function in selkies-native.sh now clones the full Selkies repo, builds both selkies-web-core (first) and selkies-dashboard, and serves the dashboard's dist/ as the web root. This guarantees the sidebar UI is present and prevents the common "no sidebar" bug.
  • Documentation in SKILL.md is updated to emphasize that the web client must be selkies-dashboard, not selkies-web-core, and details the correct build order and troubleshooting steps. [1] [2]
  • The install script and log messages now clearly indicate the dashboard is being built and served, not just the core.

Autostart shell hook robustness:

  • The autostart shell hook in both the template (autostart.bashrc) and script generator now correctly terminates the command group with a semicolon before the closing brace, preventing syntax errors in .bashrc and ensuring reliable startup. [1] [2]

Troubleshooting and reference documentation:

  • A new reference file, web-client-no-sidebar.md, provides a detailed diagnosis and fix recipe for the "no sidebar" issue, including how to confirm which client is served and how to build and verify the correct dashboard UI.

@greptile-apps

greptile-apps Bot commented Aug 23, 2026

Copy link
Copy Markdown

Greptile Summary

This PR changes the Selkies web-client installation to build and serve the standalone dashboard rather than bare web-core, fixes the generated autostart hook syntax, and adds no-sidebar diagnostic guidance.

  • Clones the full Selkies source tree and builds web-core before the dependent dashboard.
  • Deploys the dashboard distribution as the served web root.
  • Documents how to identify and repair a bare-core deployment.
  • Adds the required command separator to generated and templated autostart hooks.

Confidence Score: 4/5

The PR should not merge until web-client build and deployment failures are propagated instead of allowing installation to complete with an unusable frontend.

The new multi-stage dashboard build has no fail-fast checks, and the final successful directory listing can hide earlier npm or copy failures after the existing web root has been cleared.

Files Needing Attention: .devcontainer/skills/codespace-webtop/scripts/selkies-native.sh

Important Files Changed

Filename Overview
.devcontainer/skills/codespace-webtop/scripts/selkies-native.sh Builds and deploys the dashboard correctly in the success case, but fails to propagate build or copy errors and can report installation success with an unusable web root.
.devcontainer/skills/codespace-webtop/references/web-client-no-sidebar.md Adds a focused diagnosis and recovery procedure explaining the distinction between bare web-core and the standalone dashboard.
.devcontainer/skills/codespace-webtop/templates/autostart.bashrc Corrects the brace-group syntax by adding the required semicolon before the closing brace.
.devcontainer/skills/codespace-webtop/SKILL.md Updates installation, troubleshooting, and build-order documentation to describe the dashboard-based web client.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Clone Selkies repository] --> B[Install and build web-core]
  B --> C[Dashboard prebuild copies selkies-core.js]
  C --> D[Build dashboard]
  D --> E[Replace web_root with dashboard dist]
  E --> F[Selkies serves dashboard through nginx]
Loading
Prompt To Fix All With AI
### Issue 1
.devcontainer/skills/codespace-webtop/scripts/selkies-native.sh:264-265
**Addon build failures are ignored**

When dependency installation or either addon build fails, `cmd_build_web` continues, can clear `web_root`, and can return success from the final `ls`; `cmd_install` then creates the installed marker and reports completion even though Selkies has an empty, stale, or incompatible frontend.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "feat: update selkies web client build pr..." | Re-trigger Greptile

Comment on lines +264 to +265
build_addon "$web_core_dir"
build_addon "$dashboard_dir"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Addon build failures are ignored

When dependency installation or either addon build fails, cmd_build_web continues, can clear web_root, and can return success from the final ls; cmd_install then creates the installed marker and reports completion even though Selkies has an empty, stale, or incompatible frontend.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .devcontainer/skills/codespace-webtop/scripts/selkies-native.sh
Line: 264-265

Comment:
**Addon build failures are ignored**

When dependency installation or either addon build fails, `cmd_build_web` continues, can clear `web_root`, and can return success from the final `ls`; `cmd_install` then creates the installed marker and reports completion even though Selkies has an empty, stale, or incompatible frontend.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

@gitricko
gitricko merged commit 0216d22 into main Aug 23, 2026
7 checks passed
@gitricko
gitricko deleted the webtop-improvements branch August 23, 2026 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants