Rojo Chat: LLM Tools
Allow users to define and use tools in rojo-chat-panel. Tools extend the LLM
with callable functions (e.g. file read, web search, custom actions). The chat
panel should support declaring a tool set, passing tool definitions to the model,
handling tool-call responses, and feeding results back into the conversation.
Rojo Chat: Claude API
Integrate the Claude API (Anthropic) as a provider option in rojo-chat-panel.
Allows testing and using Claude models alongside the existing OpenAI-compatible
provider. Covers API key configuration, model selection, and verifying streaming
and tool-use work end-to-end with the Anthropic SDK.
Mobile: editor layout too tall, chat input not reachable
On mobile the overall editor layout is still too tall — panels overflow the
viewport and the chat input area is pushed out of view even after the
min-height: 0 fix on rojo-chat-panel. Needs a broader mobile layout pass
on the panel/section/editor structure.
Code syntax highlighting in rojo-chat (Highlight.js)
Code blocks in assistant responses are rendered as plain text inside pre/code tags.
Integrate Highlight.js to apply syntax highlighting after markdown-it renders each
response chunk. Apply highlighting to all code blocks in the assistant bubble.
Rojo Character Editor
Allow changing colors and selecting layers of a Rojo character from within
the rojo-settings-panel. Colors map to fill/stroke/both targets on SVG elements;
layers toggle visibility of named groups or swap between variants.
The appearance field (colors[], layers[]) is already in the settings.rojo schema.
Rojo Character Animation Box
Animation system for emotional feedback during conversations.
Animations can be scripted (predefined sequences) or driven dynamically by
an LLM that emits emotion tags alongside its response. The animation box
plays character animations (idle, happy, thinking, surprised, etc.) in the
portrait area of the rojo-settings-panel and rojo-chat-panel.
File tree: drag-and-drop move for files and directories
Allow files and directories to be moved by dragging them within the file tree.
Dragging a file onto a directory moves it inside; dragging a directory onto another
directory moves the whole subtree. Use the existing file rename API
(POST /api/files/:projectId/rename) — moving is a rename to a new parent path.
Tab context menu on right-click (tabs and empty tab bar area)
The tab ⋮ menu already works but should also open on right-click anywhere on
the tab bar — both on individual tabs and on the empty space to the right of the tabs.
Right-clicking a specific tab should also offer a "Close this tab" action directly.
Unauthenticated Landing Screen
Unauthenticated users currently crash on dashboard components.
They should land on a screen that explains the app and shows a login link.
Replace browser confirm() in group editor and account delete
The group editor and account delete button still use the browser confirm() dialog.
Replace with the custom <confirm-dialog> component already used elsewhere.
MediaViewerPanel for images and PDFs
Non-text files (images, PDFs) are visible in the file tree but not openable.
Add a MediaViewerPanel and register it in FileEditorRegistry for common media types.
Investigate Gitea webhook auto-deploy
The webhook did not fire on the last two pushes to main. Check the Gitea
webhook delivery log for the response code from /api/deploy. Also run
journalctl -u roject -n 100 on the server to see whether the endpoint
was reached at all. Most likely causes: signature mismatch, wrong branch
ref, or the deploy command failing silently.
Roject: wire lookup-email for member storage migration
The rokojori-auth side (POST /api/auth/lookup-email) is live.
Remaining Roject-side work:
— Add SERVICE_SECRET to Roject .env (must match rokojori-auth SERVICE_SECRET)
— In POST /api/projects/:id/members: call account.rokojori.com/api/auth/lookup-email,
receive the user ID, store member_id as the user ID instead of the email
— In source/server/projectAccess.ts change memberMatchesUser()
from member.member_id === user.email
to member.member_id === user.userId
— Write a one-off migration script: for each member row, call lookup-email
with the stored email and replace member_id with the returned user ID
Switch Gitea webhook to dev branch
The Gitea webhook currently triggers on pushes to main, redeploying on every commit.
Switch to a dev branch so main is the stable release target.
Ensure time is not depending on the user's clock
JWT verification on the local server failed because the Windows client clock was
~65 minutes ahead of the production auth server clock. Any time-based logic that
compares client-side time against server-issued timestamps (JWT exp, token TTL,
session validity) is broken when clocks diverge.
Work to do:
— Audit all places where Date.now() / new Date() is used for security or
session decisions; replace with server-authoritative time where possible.
— On the auth side: use clockTolerance in jwt.verify as a configurable
escape hatch (JWT_CLOCK_TOLERANCE env var, already added for local dev).
— Write a developer guide covering: why user/client clock cannot be trusted,
how to use server time for all authoritative checks, how to diagnose clock
skew issues, and the JWT_CLOCK_TOLERANCE workaround for local dev.
— Consider syncing advice in the local dev setup docs (future local-dev task).
rokojori-tunnel — Phase 2
Production-deployed at tunnel.rokojori.com. Complete so far:
relay server, CRUD API, streaming WebSocket protocol (res_start / res_data / res_end),
HTTP proxy with SSE streaming, Electron Tunnel Agent (tray, login, tunnel list),
Roject browse-tunnels button, Roject LLM chat via tunnel, client-side chunk animation.
Remaining:
— Allowed users list enforcement (multi-user private access)
— Public access mode (no auth required on proxy route)
— GET /api/tunnels/available with ?purpose= filter surfaced in Roject provider picker
styles.rokojori.com — complete deployment
Service is built and running manually via npm start on the server.
Remaining work:
— Set up systemd service (styles-rokojori.service) so it survives restarts
— Download Barlow from /add-fonts (weights 100, 400, 700, 900)
— Verify CORS is working for roject.rokojori.com font imports
— Add to the add-subdomain deployment guide as a reference example
File tree: UX improvements
— Open-state preservation: refresh() now records which ftp-dir elements are open
(via data-path on their ftp-dir-label) before rebuilding the HTML, then
re-adds the open class to matching labels after render.
— "Mark As Root Directory" moved from dblclick to context menu (isDir detection
via targetPath.endsWith('/'), shown inside showItemMenu).
— "Open >" submenu for files: context menu lists the default editor plus all
registered alternatives (_panelTypeMap / _editorAlternatives static maps).
Selecting an entry calls _openFileIn(path, editorTag).
— Context menu label: shows filename only, truncated to menuLabelMaxChars (20)
with a leading "..." prefix when over the limit.
Page editor: mode buttons moved into toolbar
The left sidebar (.pep-sidebar) and its .pep-main wrapper were removed.
The Blocks (⊞) and Areas (T) mode buttons now live directly in .pep-toolbar,
pushed right by a .pep-toolbar-sep spacer (flex: 1).
page-editor-panel now uses flex-direction: column with three direct children:
.pep-toolbar, .pep-mode-panel, iframe.
EditorConsole + console-panel
EditorConsole is a new standalone singleton (source/editor/EditorConsole.ts)
that holds a capped ring of 500 ConsoleMessage objects and dispatches them via
onMessage: EventSlot. editor-shell subscribes and shows messages in a new
.es-info element in the header (5 s fade; portrait: fixed bottom bar).
Editor.onFileTypeUnknown is bridged to EditorConsole here, removing the
inline ftp-type-error element from file-tree-panel.
console-panel is a new tab that renders all messages from EditorConsole using
custom elements (conp-header, conp-list, conp-entry, conp-time, conp-text).
Added to tab-container panel-type list and loaded in editor.html.
Bug fix: openDocumentIn ignored the target panel type
openDocumentIn was re-resolving editorTag from FileEditorRegistry, which always
returned the default editor for the file type (e.g. page-editor-panel for .page
files). The code-panel listener checks editorTag and bailed, so files opened
via "Open in Code Editor" showed a blank panel.
Fix: derive editorTag from panelElement.tagName.toLowerCase() directly,
removing the registry lookup from openDocumentIn entirely.