fix(atlas): wire the canvas Initialize button to the deterministic endpoint#114
Merged
Merged
Conversation
…dpoint
The 'initialize this project's graph' button dropped '/initialize-atlas-graph'
into the chat composer and sent it, delegating graph creation to the AGENT —
inheriting every fragility of the prompt path (skipped when the atlas binary
is absent, or on short tasks). Meanwhile initGraph(), which calls
thesisAPI.initProject → POST /api/thesis/project/init (the proven
find-or-create endpoint) and then refetches + selects the new root, was
defined but wired to nothing, and busy={initializing()} was dead.
Point the primary button at initGraph() so it deterministically creates the
graph without the agent or the atlas binary, and surfaces a typed error toast
on failure. The secondary 'chat' action still drops the skill invocation for
review when the user wants to resolve a plan/auth issue in chat.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The web half of "Atlas doesn't create the graph."
Bug
The canvas's "initialize this project's graph" button dropped
/initialize-atlas-graphinto the chat composer and sent it — i.e. it asked the agent to create the graph, inheriting every fragility of the prompt path (skipped when theatlasbinary is absent, or on a short task). MeanwhileinitGraph()— which callsthesisAPI.initProject→POST /api/thesis/project/init(the deterministic find-or-create endpoint that returns aproject_id), then refetches and selects the new root — was defined but wired to nothing (dead code), andbusy={initializing()}was dead with it.Fix
Point the primary button at
initGraph()so it deterministically creates the graph without the agent or theatlasbinary, and toasts a typed error on failure (initializing()now drives the busy state). The secondary "chat" action still drops the skill invocation (without sending) so the user can review/run it — handy when the direct call reports a plan/auth issue to resolve in chat.Verification
typecheck(workspacetsgo -b) +prettierclean;bun run --cwd frontend/workspace buildsucceeds.