mirror of
https://github.com/ZSeven-W/openpencil.git
synced 2026-06-01 03:14:29 +07:00
5 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kayshen Xu
|
904c033290
|
V0.7.2-bugfix (#109)
* Stabilize synced main for AI handoff, drag nesting, and Electron dev (#104) * docs(readme): update cover screenshot * fix: stabilize electron dev sync and codex env passthrough * Preserve nested frame behavior during drag reparenting Reparenting across containers used raw local coordinates and root-only clipping assumptions, which made nodes jump visually and caused dragged frames to lose clip/corner semantics after nesting. This adapts the drag-reparent fix to the current upstream store architecture, keeps frame/shape nodes from auto-detaching on canvas drags, and promotes formerly root-only frame clipping to explicit clipContent when nested. Constraint: Latest upstream workspace checkout is incomplete locally (missing workspaces/deps), so full upstream verification could not be rerun in this environment Rejected: Keep using raw local x/y during parent changes | fails for auto-layout/padding-rendered positions Rejected: Make all nested frames clip unconditionally | would change non-clipping containers Confidence: medium Scope-risk: moderate Reversibility: clean Directive: Preserve visual-position conversion through rendered coordinates when parent changes; local coordinates alone are insufficient once layout participates Not-tested: Fresh full workspace typecheck/test/build on latest upstream checkout (blocked by missing workspace/dependency setup in this local clone) * Keep AI codegen requests bounded while exporting asset bundles The AI codegen pipeline needed two stability fixes: exported design images had to flow through chunk/assembly prompts as reusable asset hints, and oversized chat payloads needed a local guard before hitting provider limits. This commit wires asset extraction into the planning pipeline, threads exported asset paths into prompt assembly, and rejects obviously overlarge chat requests with an actionable client-side error. Constraint: This branch is split out from a larger local fix stack, so only codegen/prompt/context files are included here Constraint: Provider request limits are approximate locally, so the payload guard must be conservative rather than exact Rejected: Inline base64 assets directly into prompts | explodes request size and repeats the same payload per chunk Rejected: Let provider errors handle oversized payloads | too slow and opaque for users Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep asset references flowing as stable ./assets paths and enforce payload limits before fetch to avoid silent request bloat Tested: bun x tsc -p apps/web/tsconfig.json --noEmit; cd apps/web && bun --bun vitest run src/services/ai/__tests__/context-optimizer.test.ts src/services/ai/__tests__/codegen-assets.test.ts src/services/ai/__tests__/structure-bundle.test.ts; bun run build Not-tested: Manual end-to-end AI generation with live providers * Explain sanitized design views instead of leaving AI to guess The sanitized structure bundle already stabilized asset paths, but it still exposed low-level image/layout/component fields that models had to interpret on their own. This change adds explicit consumer-view enrichment for fills, layout, text, variables, themes, and component semantics, carries original image size through the Figma import path, and augments sanitized bundles with summary/highlight guidance for downstream AI consumers. Constraint: This branch is intentionally stacked on the asset-bundle PR because it extends the sanitized/codegen asset pipeline rather than replacing it Constraint: Figma import data is not always complete, so original image size must be preserved when present and inferred only as a fallback downstream Rejected: Keep sanitized.json as a pure field-level dump | still leaves AI to misread transforms, layout, and component relationships Rejected: Put all explain text directly in asset extraction helpers | mixes resource stabilization with semantic enrichment responsibilities Confidence: high Scope-risk: moderate Reversibility: clean Directive: Treat consumer-view enrichment as a distinct layer on top of stable asset extraction; future AI-facing semantics should land there instead of leaking into unrelated pipeline code Tested: bun x tsc -p apps/web/tsconfig.json --noEmit; cd apps/web && bun --bun vitest run src/services/ai/__tests__/consumer-view-enrichment.test.ts src/services/ai/__tests__/codegen-assets.test.ts src/services/ai/__tests__/structure-bundle.test.ts ../../packages/pen-figma/src/figma-fill-mapper.test.ts; bun run build Not-tested: Manual prompt-to-code generation quality with live provider responses * Restore code-panel bundle exports for AI handoff flows The code generation backend still produced asset manifests and AI structure bundles, but the code panel UI no longer exposed those export paths after later sync work. This commit reconnects the panel to bundle export actions, restores ZIP download behavior when generated code includes exported assets, and locks the affordances with focused panel tests. Constraint: Other local fixes are still in progress in the working tree, so this commit is intentionally limited to the code-panel export surface Rejected: Rebuild export support in a separate panel | users expect the export actions to remain where generation results are shown Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep code-panel UI aligned with codegen asset/bundle backends whenever generation result shape changes Tested: cd apps/web && bun --bun vitest run src/components/panels/code-panel.test.tsx src/services/ai/__tests__/codegen-assets.test.ts src/services/ai/__tests__/structure-bundle.test.ts; bun run build Not-tested: Manual click-through of AI Bundle and Download ZIP in the desktop/web UI * Unblock electron dev startup in the incomplete local workspace The local workspace was failing before the app could even start: the skills plugin hard-required js-yaml from a node_modules layout that was not present, Vite dev under Bun hit Nitro NodeResponse incompatibilities, and the web tsconfig was missing path mappings for local packages. This commit removes the unnecessary js-yaml dependency from the skills loader, runs Vite under Node for dev startup, hardens readiness probing with socket checks, and points TypeScript/Vite at the in-repo package sources. Constraint: The current local clone has incomplete hoisted/workspace installation state, so dev startup must not depend on root package links being perfectly present Constraint: Bun + Nitro dev currently mis-handle NodeResponse in this environment, so the safest startup path is Node-hosted Vite Rejected: Keep js-yaml and require everyone to fix local hoisting first | still leaves electron:dev broken in the current environment Rejected: Continue running Vite dev through Bun | reproduces the NodeResponse/Parse Error failure on /api and /editor requests Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep the dev launcher biased toward resilient local startup, even when the workspace install shape is imperfect Tested: bun -e import('./packages/pen-ai-skills/vite-plugin-skills.ts').then(() => console.log('SKILL_PLUGIN_IMPORT_OK')); bun electron:dev verified Vite ready, MCP/Electron compiled, Electron launched, MCP sync log emitted Not-tested: Long-running interactive desktop session after startup * fix(figma): preserve cropped image fill transforms The synced branch started exporting original image dimensions but dropped the existing crop transform semantics from the shared image-fill type and both Figma mappers. That broke the new regression test and stripped metadata that AI consumer-view/bundle code already relies on. Constraint: keep app and package Figma mappers in lockstep Rejected: loosen the new regression test | would hide a real metadata regression Confidence: high Scope-risk: narrow Reversibility: clean Directive: when extending image fill metadata, update shared pen-types and both Figma mapper copies together Tested: bun --bun run test (148/149 files passed; only server/__tests__/sse-keepalive.test.ts blocked by missing agent_napi.node), cd apps/web && bun --bun vitest run src/canvas/skia/drag-reparent-policy.test.ts src/components/panels/layer-dnd-utils.test.ts src/stores/document-position-utils.test.ts src/components/panels/code-panel.test.tsx ../../packages/pen-renderer/src/__tests__/document-flattener.test.ts ../../packages/pen-figma/src/figma-fill-mapper.test.ts, cd apps/web && bun --bun vitest run src/services/ai/__tests__/codegen-assets.test.ts src/services/ai/__tests__/structure-bundle.test.ts src/services/ai/__tests__/consumer-view-enrichment.test.ts, cd apps/web && bun --bun vitest run src/utils/__tests__/security.test.ts, bun test scripts/loopback-no-proxy.test.ts, npx tsc --noEmit, bun --bun run build Not-tested: server/__tests__/sse-keepalive.test.ts without a locally built @zseven-w/agent-native addon * docs(editor): normalize new PR comments to English The PR had a handful of newly introduced Chinese code comments in dev, sync, and AI helper paths. This follow-up keeps the implementation unchanged while translating those comments to English so the PR stays consistent with the repository comment-language expectation. Constraint: The request was limited to comment language cleanup after the conflict-resolution merge, so behavior had to remain unchanged Rejected: Leave the mixed-language comments in place | conflicts with the PR requirement for English comments Rejected: Broader repository-wide translation sweep | unnecessary scope expansion beyond the PR-introduced comments Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep code comments in English on this branch, even when local notes or working memory are in another language Tested: bun test scripts/loopback-no-proxy.test.ts apps/desktop/__tests__/dev-utils.test.ts; cd apps/web && bun --bun vitest run server/__tests__/mcp-sync-state-active.test.ts src/canvas/skia/__tests__/skia-interaction.test.ts; npx tsc --noEmit; branch-diff comment scan for Han characters in comment lines Not-tested: Manual runtime behavior, since this change only rewrote comments * style(editor): apply repository formatting expected by CI The PR was failing the CI Format check after the conflict-resolution and comment-normalization follow-ups. This commit applies the repository formatter output to the files touched by the branch so CI sees the exact formatting it expects, without changing behavior. Constraint: The failing GitHub Actions job stopped at Format check, so the fix had to match oxfmt output rather than introduce functional changes Rejected: Leave the branch as-is and rely on local formatting differences being acceptable | CI explicitly rejects the current formatting Rejected: Broader code cleanup beyond formatter output | unnecessary scope while repairing the failing check Confidence: high Scope-risk: narrow Reversibility: clean Directive: After conflict resolution or comment-only edits on this repo, run bun run format:check before pushing because formatter expectations are stricter than the existing file style in some touched files Tested: bun run format:check; bun run lint; npx tsc --noEmit Not-tested: Full test suite after this formatting-only commit (previous run showed formatting was the first CI blocker) * refactor(editor): remove proxy-specific dev workarounds from PR The PR no longer needs the loopback proxy bypass layer, so this cleanup removes the proxy-specific dev entrypoint, environment bootstrap, helper module, and its tests while keeping the unrelated Electron and AI handoff changes intact. Constraint: Removal had to be limited to proxy-related code on PR #104 without undoing the other merged fixes on the branch Rejected: Keep the helper and stop using it | leaves proxy-specific maintenance surface and tests in the PR Rejected: Revert the entire Electron dev file to upstream earlier than necessary | would risk dropping unrelated local conflict-resolution choices beyond the proxy scope Confidence: high Scope-risk: moderate Reversibility: clean Directive: If proxy handling is reintroduced later, keep it out of this PR unless there is a dedicated, separately justified change for it Tested: bun run format:check; bun run lint; npx tsc --noEmit Not-tested: Manual electron:dev behavior after removing the proxy-specific launcher path * docs(ai): translate JSON-facing semantic descriptions to English The PR still emitted Chinese semantic description strings inside the AI consumer-view and structure-bundle JSON outputs. This change translates those JSON-facing runtime descriptions and updates the affected tests so exported AI-facing structure data is consistently English. Constraint: The request was limited to JSON description strings, so the change had to preserve the same semantics and structure while only translating output text Rejected: Leave Chinese test fixtures and runtime descriptions in place | conflicts with the requirement for English JSON descriptions Rejected: Broader i18n cleanup outside these AI JSON description paths | unnecessary scope expansion beyond the requested exported-description surface Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep AI/exported JSON explanation strings in English unless a future change explicitly adds localized output modes Tested: cd apps/web && bun --bun vitest run src/services/ai/__tests__/consumer-view-enrichment.test.ts src/services/ai/__tests__/structure-bundle.test.ts src/services/ai/__tests__/codegen-assets.test.ts; bun run format:check; npx tsc --noEmit Not-tested: Full app runtime flows that consume these JSON descriptions outside the covered unit tests * refactor(ai): remove remaining network-proxy handling The current project still carried Anthropic proxy-specific heuristics and environment handling outside the PR-specific cleanup. Since the earlier crashes and connectivity issues were unrelated to proxying, this removes the remaining network-proxy branches, model remapping, and TLS override advice while leaving unrelated request flows intact. Constraint: The cleanup needed to remove proxy-specific logic without disturbing unrelated transport concepts such as app-internal API proxy routes or React proxy objects used in tests Rejected: Keep the proxy heuristics as dormant fallback logic | preserves misleading operational guidance and dead maintenance surface Rejected: Rename every remaining literal use of the word proxy in the repo | would overreach into unrelated concepts like internal API proxying and JS Proxy-based test setup Confidence: medium Scope-risk: moderate Reversibility: clean Directive: If endpoint-specific compatibility logic is needed later, add it as explicit endpoint handling rather than generic proxy heuristics Tested: bun run format:check; bun run lint; npx tsc --noEmit; repo-wide search for network-proxy env references after cleanup Not-tested: End-to-end Claude connection flows against custom base URLs after removing proxy-specific remapping * fix(electron): keep Node-backed dev launch for Nitro compatibility Comparing against upstream commit |
||
|
Kayshen Xu
|
e20957b740
|
V0.7.0 (#95)
* fix(agent): fix race condition causing 'no text output' on successful tool calls
The done event arrives via SSE before the executor's .then() callback
updates toolCallBlock status from 'running' to 'done'. Checking
status === 'done' at that moment finds nothing, showing the wrong message.
Fix: check if any tool calls exist (length > 0) instead of their status.
If the agent made tool calls and finished normally, the work was done.
* fix(ai): normalize built-in provider base urls
* fix(agent): preserve thinking steps in done handler, don't show empty fallback
The done handler called updateLastMessage(accumulated) which overwrote
the previously displayed thinking steps. Now:
- If tool calls + no text: show "Design generated successfully" with thinking prefix
- If thinking + no text + no tools: keep thinking steps, no fallback message
- If nothing at all: show "Agent completed with no text output"
* chore(agent): add diagnostic logging for agent event stream
* feat(agent): update submodule with tool_use SSE parsing support
* fix(agent): handle tool_use events in zigEventToSSE, suppress incomplete content_block_start
Two issues:
1. content_block_start with tool_name was forwarded as tool_call with
empty args {} (partial_json not yet accumulated). Client dispatched
generate_design with no prompt → error.
2. The complete tool_use event from Zig engine was not handled by
zigEventToSSE → mapped to 'unknown' type → client ignored it.
Fix: add tool_use branch to zigEventToSSE (maps to tool_call with full
args), suppress content_block_start tool calls (return empty string).
* feat(agent): make team mode mandatory when concurrency >= 2, force parallel designers
* feat(ai): add coding plan provider presets
* fix(ai): sync provider preset URL normalization from upstream
Includes canonicalize helpers, legacy URL migration, and region support
for Zhipu, GLM Coding, Kimi, Bailian, StepFun presets.
* test(ai): add preset URL chat/completions endpoint verification
Validates all 13 openai-compat provider presets produce correct
final URLs when combined with agent-native's /chat/completions suffix.
* feat(ai): extend RoleDefaults type with fill, stroke, effects
* feat(ai): add visual defaults to role definitions (fill, stroke, shadow)
* feat(ai): add hexLuminance and hasFill helpers for visual post-pass
* chore(agent): bump agent-native submodule to 2a57ee9
* feat(ai): add button foreground contrast post-pass fix
* feat(ai): add section background alternation post-pass fix
* feat(ai): add orphan container contrast post-pass fix
* feat(ai): add input sibling fill/stroke consistency post-pass fix
* feat(ai): enrich agent tool instructions with design quality brief
Also fix test mock for canvas-text-measure and TS cast in button
foreground contrast.
* feat(ai): infer semantic role from node name for models that don't set role
Weak models (e.g. minimax) often output nodes without the `role` property,
causing all visual defaults to be skipped. This adds name-based inference
that maps common node names (Button, Card, Search, Nav, etc.) to semantic
roles before applying defaults.
* feat(ai): intercept raw design JSON from agent and re-route through orchestrator
Some models (e.g. minimax-m2.5) ignore tool-calling instructions and output
design JSON directly as text instead of calling generate_design. This bypasses
the orchestrator pipeline (spatial decomposition, sub-agents, role resolution).
When the agent stream ends without any tool activity but the accumulated text
contains design JSON, extract the user's original prompt and re-generate
through generateDesign() for proper quality.
* feat(store): add panelWidth, panelHeight, isMaximized to AI store
* fix(ai): detect mobile intent and force 375x812 canvas in orchestrator re-route
When the agent intercept re-routes through generateDesign(), detect mobile
keywords (mobile, 手机, 移动端, app, ios, android, etc.) in the user prompt
and force canvas size to 375x812 instead of using the viewport size.
* fix(ai): clean up inline nodes before orchestrator re-route
When feedText() already inserted nodes during agent text streaming,
remove them before calling generateDesign() to avoid duplicate designs
on canvas.
* refactor(ai): remove feedText() from agent text streaming
Agent text output should never insert nodes inline — if the agent outputs
design JSON as text, the done handler re-routes through generateDesign().
Removes feedText() call and the now-unnecessary cleanup code.
* i18n: add keys for chat panel redesign, file menu, and unsaved dialog
* feat(ai): redesign quick actions to 2x2 card grid with descriptions
* feat(store): add recent files persistence utility
* feat(editor): add UnsavedChangesDialog component
* refactor(ai): simplify agent prompt and remove orchestrator re-route
Shorten AGENT_TOOL_INSTRUCTIONS to 4 clear rules that weak models can
follow: use tools, never output JSON, summarize after tool calls, add
style direction. Remove the complex interceptor that re-called
generateDesign() when the agent output raw JSON — the goal is to make
the agent reliably call the tool in the first place.
* feat(ai): move send/attach buttons into textarea, simplify bottom bar
* feat(editor): add FileMenu dropdown component with recent files
* fix(ai): strengthen generate_design result to prevent double calls
The tool result now explicitly tells the agent "Do NOT call
generate_design again — the task is done" to prevent weak models
from retrying after a successful generation.
* feat(ai): upgrade chat panel to freely resizable window with maximize
* fix(ai): retry sub-agent once on socket close or empty response
When a sub-agent stream fails (e.g. provider socket closed unexpectedly),
retry the subtask once before throwing. This handles transient connection
issues with providers like ark/volces that occasionally drop SSE streams.
* feat(editor): integrate file menu dropdown and recent files into top bar
* fix(ai): move send/attach buttons back to bottom bar with cleaner layout
* feat(editor): replace window.confirm with UnsavedChangesDialog
* refactor(editor): move file menu to left toolbar dropdown, clean up top bar
* fix(editor): add chevron indicator to file menu button
* feat(electron): add Save As, Open Recent to native File menu with recent files sync
* style(editor): redesign UnsavedChangesDialog with icon, glow ring, and stacked layout
* style(editor): redesign unsaved dialog with dark glass morphism and animated glow border
* fix(ai): keep SSE ping alive during builtin provider streaming
streamViaBuiltin() cleared the ping timer on the first SSE event,
leaving no keep-alive for the rest of the stream. If the provider
paused for >10s (thinking, slow generation), Bun's idle timeout
killed the connection. The ping timer is already cleared in the
finally block — removing the premature clearInterval.
* fix(editor): add light/dark theme support to UnsavedChangesDialog
* fix(ai): remove conflicting design knowledge from agent system prompt
The agent prompt combined AGENT_TOOL_INSTRUCTIONS ("FORBIDDEN: do not
output JSON") with pen-ai-skills design knowledge ("you MUST output
JSON"). These contradictory instructions caused weak models to ignore
tool calling. Agent mode now only gets tool instructions — design
knowledge is loaded by the orchestrator sub-agents.
* style(editor): refine unsaved dialog with staggered entry, grain texture, and breathing glow
* fix(ai): abort builtin engine after 60s of no SSE events
When a provider returns 200 OK but never sends SSE data, the Zig
readChunk blocks forever. Add a 60s timer that calls abortEngine()
to unblock the Zig thread, allowing the stream to end gracefully
and the orchestrator to retry or fail fast.
* fix(ai): skip orchestrator planning API for builtin providers
Builtin providers (minimax, etc.) consistently return empty responses
for the long planning system prompt. Skip the planning API call and
use the heuristic fallback plan directly — same result without the
60s timeout wait and wasted API call.
* feat(ai): add plan_layout + batch_insert tools for builtin provider design
For builtin providers (API key direct), the agent now uses plan_layout
and batch_insert tools instead of generate_design. This avoids the
orchestrator's multi-step API calls that unreliable providers can't
handle.
Flow:
1. Agent calls plan_layout(prompt) → creates root frame, returns sections
2. Agent generates PenNode JSON itself
3. Agent calls batch_insert(parentId, nodes) → inserts with role defaults
No extra API calls — the agent's single LLM connection handles everything.
CLI providers still use generate_design → orchestrator pipeline.
* fix(ai): remove design knowledge from builtin agent prompt to prevent JSON output
* fix(ai): prevent duplicate plan_layout calls with layoutCreated guard
* fix(ai): builtin generate_design creates layout frame instead of orchestrator
For builtin providers, generate_design now delegates to plan_layout
(creates root frame) and returns the layout info to the agent. The
agent then generates PenNode JSON and calls batch_insert — no
orchestrator, no extra API calls. CLI providers still use the full
orchestrator pipeline.
* fix(ai): minimize generate_design tool result to reduce token usage
* fix(ai): limit builtin agent to 5 turns to prevent token overflow
* fix(ai): keep long-running sse streams alive
* fix(ai): stop duplicate builtin design runs
* fix(ai): restore typecheck after rebase
* fix(ai): align builtin single-agent tooling
* fix(ai): guard builtin layout loops
* feat(ai): builtin agent uses full generate_design pipeline with streaming
- Remove normalizeKnownMalformedOpenAICompatURL — URL version detection
now handled in agent-native Zig layer
- Builtin agent uses same generate_design orchestrator pipeline as CLI
(StreamingDesignRenderer, breathing glow, skills)
- Fix streamViaBuiltin event parsing — was checking evt.type instead of
evt.stream_event.type, silently dropping all text/thinking events
- Add max_output_tokens/max_context_tokens passthrough in agent endpoint
- Fix tool completion status — add .then() handler to update tool block
to 'done' after execution (was stuck on 'running' forever)
- plan_layout reuses existing root frame via getActivePageChildren()
- batch_insert: breathing glow with random agent identity, streaming
insertion (3-node batches), max 9 nodes per call
- Mobile section element hints prevent Header/Main Content duplication
- Default background #FFFFFF, suppress thinking text in progress steps
- maxTurns unified to 20 for all providers
* fix(agent): lower default max_output_tokens to 16384
Update agent-native submodule — 200K default caused 400 errors on
providers with lower token limits (Volcengine, MiniMax, etc.).
* fix(ai): restore generate_design tool for builtin agent
Remote merge introduced getBuiltinLeadToolDefs() which filtered out
generate_design, reverting builtin agents to plan_layout+batch_insert.
Use getDesignToolDefs() for all agents to ensure the full orchestrator
pipeline is used.
* fix(ai): prevent duplicate content in mobile fallback plan and restore builtin planning
- Use single subtask for mobile fallback plan instead of Header/Main Content
split that caused both sub-agents to generate overlapping UI elements
- Remove login-screen-specific element hints that misled food/general app generation
- Always attempt AI planning for builtin providers (with 30s/60s fast timeout)
instead of unconditionally skipping — callOrchestrator already has internal
fallback for unparseable responses
- Respect user abort during planning — check abortSignal after streaming ends
to prevent fallback plan from continuing canvas mutations
* fix(ai): clean up root frames when sub-agent execution fails
Remove root frames created in Phase 2 before re-throwing, so the
canvas doesn't strand empty frames when orchestration fails after
canvas setup.
* fix(ai): only remove empty root frames on sub-agent failure
Check whether root frames have children before removing them, so
partial output from earlier successful subtasks is preserved.
* fix(ai): detect scaffold-only frames in failure cleanup
Snapshot descendant count after Phase 2 setup and compare on failure.
Only remove root frames whose descendant count hasn't grown beyond
scaffold nodes (status bar, dashboard columns), preserving frames
that received real sub-agent content.
* fix(ai): restore default frame instead of deleting it on failure
When the root frame replaced the default empty frame (DEFAULT_FRAME_ID)
and sub-agents fail, restore it to its empty state rather than removing
it, so the canvas always retains a usable frame.
* fix(ai): fully replace default frame on failure instead of shallow merge
Remove and re-add the default frame so stale layout, gap, fill, and
scaffold children from the failed generation run are fully cleared.
* style(editor): upgrade provider form with shadcn Select, always-visible API format toggle
* fix(editor): hide API format toggle for Anthropic and OpenAI presets
* feat(editor): auto-switch baseURL on API format change, make baseURL always editable
Add dual-format URLs for providers that support both OpenAI and Anthropic:
- OpenRouter: /api/v1 (OpenAI) / /api (Anthropic)
- DeepSeek: /v1 (OpenAI) / /anthropic (Anthropic)
- MiniMax: /v1 (OpenAI) / /anthropic (Anthropic)
* style(editor): redesign provider form with compact layout, field icons, and segmented controls
* fix(editor): lock baseURL for Anthropic and OpenAI presets
* fix(editor): only show API format toggle for providers that support both formats
* refactor(editor): use presetConfig.altType to determine API format toggle visibility
* feat(editor): add Anthropic format support for Zhipu (open.bigmodel.cn/api/anthropic)
* feat(editor): add Anthropic format support for GLM Coding Plan
* feat(editor): add Anthropic format support for Kimi (api.moonshot.cn/anthropic)
* feat(editor): add Anthropic format support for Bailian/DashScope
* feat(editor): add Anthropic format support for DouBao and Ark Coding Plan
* feat(editor): add Anthropic format support for ModelScope
* feat(editor): add Bailian Coding Plan preset with dedicated endpoint and Anthropic support
* feat(editor): add altRegions for region-aware Anthropic URL switching
Providers with regions now correctly switch altBaseURL by region:
- MiniMax: minimaxi.com / minimax.io
- Zhipu: bigmodel.cn / z.ai
- GLM Coding: bigmodel.cn / z.ai
- Kimi: moonshot.cn / moonshot.ai
- Bailian: aliyuncs.com / dashscope-intl
- Bailian Coding: coding.dashscope / coding-intl.dashscope
* fix(ai): remove hardcoded blue fill from button role defaults
Button role was injecting #2563EB fill on any frame inferred as a
button, including container frames named "Button Group" or similar.
This caused mysterious blue backgrounds on non-blue themed designs.
- Remove fill from all three button role branches
- Add word-boundary matching for button name inference
- Add container-suffix exclusion to prevent "Button Group" etc.
from being inferred as button role
* feat(types): add codegen types and wire DTO types to pen-types
Migrate canonical codegen type definitions (Framework, PlannedChunk,
CodePlanFromAI, ExecutableChunk, CodeExecutionPlan, ChunkContract,
ChunkResult, CodeGenProgress, ContractValidationResult) from
pen-codegen to pen-types to establish pen-types as the authoritative
source before pen-codegen package removal.
Add new wire DTO types for MCP/CLI responses:
- NodeSnapshot: depth-limited node snapshot for wire transfer
- ExecutableChunkPayload: hydrated chunk payload with truncated nodes
- ResolvedDepContract: dependency contract with null support
Add comprehensive type tests covering FRAMEWORKS constant, NodeSnapshot
variants, and ResolvedDepContract nullability.
* feat(core): add sanitizeName and nodeTreeToSummary utilities
Migrate utility functions from pen-codegen to pen-core for broader reuse:
- sanitizeName: converts strings to PascalCase
- nodeTreeToSummary: recursively renders node trees for AI prompts
Add comprehensive tests for both utilities.
* feat(mcp): migrate validateContract from pen-codegen
Move the validateContract function into pen-mcp to support the chunked
codegen pipeline. The types (ChunkResult, ContractValidationResult) are
already re-exported from @zseven-w/pen-types (Task 1 completed).
- Create packages/pen-mcp/src/utils/validate-contract.ts
- Add re-export to packages/pen-mcp/src/index.ts
- Add 4 test cases validating PascalCase, code presence, and SFC detection
* feat(mcp): implement read_nodes handler with depth-limited subtree fetching
Adds handleReadNodes() in pen-mcp that supports depth=-1 (full tree),
depth=0 (node only), and depth=N (N levels of children), reusing the
existing readNodeWithDepth utility. Includes 7 Vitest tests.
* feat(editor): implement App-side codegen plan state store
Adds in-memory plan store with createPlan, getPlan, submitChunkResult,
assemblePlan, and cleanPlan. Validates duplicate chunkIds, empty nodeIds,
unknown/circular dependencies, and missing nodes. Hydrates ExecutableChunkPayload
with NodeSnapshot[] and resolved dep contracts. TTL-based expiry (30m).
* fix(codegen): export PlanState interface and narrow statusOverride type
- Export PlanState interface for public API (getPlan returns PlanState | undefined)
- Narrow submitChunkResult statusOverride parameter from ChunkStatus to 'failed' | 'skipped'
(only these two values have defined semantics in the validation logic)
* feat(mcp): add HTTP endpoints for read_nodes and incremental codegen pipeline
Adds five Nitro route handlers under /api/mcp/:
- POST read-nodes: returns node snapshots with depth-limited children
- POST codegen/plan: validates and stores a CodePlanFromAI, returns execution plan
- POST codegen/submit: submits a ChunkResult and returns next ready chunk
- GET codegen/assemble/[id]: assembles final output from completed chunks
- DELETE codegen/plan/[id]: cleans up plan state early
All routes support live canvas (getSyncDocument) and offline file (openDocument)
modes. Adds @zseven-w/pen-mcp as a workspace dependency of apps/web.
* refactor(mcp,web): dedup readNodeWithDepth and validateContract imports
Move readNodeWithDepth export from inline copy in read-nodes.post.ts to
pen-mcp for DRY, and use pen-mcp's validateContract in codegen-plan-store
instead of maintaining duplicate implementation.
- Export readNodeWithDepth from pen-mcp/utils/node-operations
- Remove inline readNodeWithDepth from apps/web/server/api/mcp/read-nodes.post.ts
- Add type cast (as unknown as NodeSnapshot) for pen-mcp readNodeWithDepth result
- Replace validateContractFn with import from pen-mcp in codegen-plan-store.ts
All 36 tests pass (4 validate-contract + 7 read-nodes + 11 plan-store + 14 security)
* feat(mcp): add codegen HTTP client handlers
Implement four thin HTTP client wrappers for codegen pipeline:
- codegen_plan: POST /api/mcp/codegen/plan — initialize plan
- codegen_submit_chunk: POST /api/mcp/codegen/submit — submit chunk result
- codegen_assemble: GET /api/mcp/codegen/assemble/:planId — assemble code
- codegen_clean: DELETE /api/mcp/codegen/plan/:planId — cleanup state
All handlers use await getSyncUrl() to discover running App, throw on missing sync
URL (except codegen_clean which gracefully returns ok). Uses encodeURIComponent for
URL path parameters. No business logic, purely HTTP clients for App endpoint integration.
* feat(mcp): register codegen tools in server and replace export_nodes
Add codegen-routes.ts with definitions and dispatcher for all 5 new tools
(read_nodes, codegen_plan, codegen_submit_chunk, codegen_assemble,
codegen_clean). Replace EXPORT_* wiring in server.ts with CODEGEN_* and
update pen-mcp public API in index.ts to export the new handlers instead
of handleExportNodes.
* feat(cli): add read-nodes and codegen pipeline commands
Add op read-nodes to query document nodes via the App HTTP API, and
op codegen:plan/submit/assemble/clean commands to drive the incremental
codegen pipeline. All five commands are stateless HTTP clients against
the /api/mcp/* endpoints. Also update help text to document the new
commands.
* refactor(codegen): migrate all pen-codegen consumer imports (Task 12)
Replace all @zseven-w/pen-codegen imports in consumer files with their
canonical new homes: types → pen-types, sanitizeName/nodeTreeToSummary →
pen-core, validateContract → pen-mcp, generator functions → pen-sdk
(which retains one pen-codegen re-export until Task 13 deletes the package).
- code-panel.tsx: Framework, CodeGenProgress, ChunkStatus, FRAMEWORKS → pen-types
- code-generation-pipeline.ts: types → pen-types, sanitizeName → pen-core, validateContract → pen-mcp
- codegen-prompts.ts: types → pen-types, nodeTreeToSummary → pen-core
- code-generation-pipeline.test.ts: CodePlanFromAI, PlannedChunk → pen-types
- design-engine.ts: remove pen-codegen import + delete generateCode() method
- design-engine.test.ts: delete generateCode test
- pen-sdk/index.ts: codegen re-export split into types (pen-types) + functions (pen-codegen)
- apps/web/src/services/codegen/*.ts: delete all 9 generator proxy files
- apps/cli: migrate export.ts to pen-sdk; add pen-sdk dependency, drop pen-codegen
* fix(cli,sdk): fix Task 12 spec violations — delete export.ts, remove pen-codegen from pen-sdk
- Delete apps/cli/src/commands/export.ts (replaced by op read-nodes + op codegen:*)
- Remove `case 'export':` dispatcher and help text from apps/cli/src/index.ts
- Remove @zseven-w/pen-sdk dep from apps/cli/package.json (only used by deleted export.ts)
- Remove generator function re-exports from pen-sdk/src/index.ts (codegen section deleted)
- Remove @zseven-w/pen-codegen dep from pen-sdk/package.json
pen-sdk now has zero imports from @zseven-w/pen-codegen, unblocking Task 13.
* chore(codegen): remove pen-codegen package entirely
All consumers have been migrated to pen-types (types) and pen-core
(utility functions) in Tasks 1-12. Delete packages/pen-codegen/ and
remove the workspace dependency from apps/web and pen-engine.
* chore(mcp): remove pen-codegen from CI, scripts, desktop, and delete old export tool files
Cleans up all remaining references to the deleted pen-codegen package from
esbuild alias flags (mcp:compile, cli:compile, desktop dev.ts), publish scripts,
and the GitHub Actions publish workflow. Deletes the superseded export-routes.ts
and export-nodes.ts MCP files that were replaced by codegen-routes.ts in Task 10.
* fix(ai): inline validateContract in code-generation-pipeline to avoid pen-mcp browser import
Importing validateContract from @zseven-w/pen-mcp pulled in document-manager
transitively, which uses node:fs/promises and broke Vite's browser bundle:
"Module node:fs/promises has been externalized for browser compatibility".
Inline the 11-line pure function instead — the original plan listed inlining
as an acceptable option for this client-side consumer.
* fix(panels): force builtin provider in code panel for builtin: models
modelGroups reports 'anthropic' or 'openai' as the provider for builtin
providers (based on bp.type), but streamChat needs 'builtin' to route
the request through streamViaBuiltin on the server. Without this, models
like minimax were sent to streamViaAgentSDK (Claude Code) which rejected
them with "There's an issue with the selected model".
Mirror the same override that ai-chat-handlers.ts already applies, so the
code panel uses the same provider routing as the chat panel.
* fix(mcp): fall back to IPv6 for live sync url discovery
Vite 6+ resolves `localhost` to `::1` only on macOS, leaving IPv4
127.0.0.1 unreachable. The MCP document-manager previously only probed
IPv4 hosts, so every batch_get / open_document / get_variables call
failed with "fetch failed" even though the dev server was running. Add
[::1] to SYNC_BASE_URLS and race all probes in parallel via Promise.any
so the first reachable host wins immediately instead of serially waiting
for IPv4 timeouts.
* fix(ai): harden post-streaming pipeline against layout and phone mockup bugs
Weaker sub-agents (MiniMax M2, GLM, Kimi) were producing two classes of
structural failures that the post-streaming passes did not handle:
1. Missing layout on container frames — children collapsed to (0,0)
because computeLayoutPositions skips frames with no explicit layout.
2. Fake "Phone Mockup" wrappers — the sub-agent pasted phone bezel
properties (cornerRadius 32, width 260, black fill, horizontal layout)
onto its own root frame and stuffed an entire duplicated section tree
inside, compressing everything into a 40px-wide column.
The root cause for #2 was that `jsonl-format.md` (loaded by every
generation sub-agent) and a line in `orchestrator-sub-agent.ts` both
injected the phone-mockup spec unconditionally. On mobile flows where
the whole design IS already a phone screen, this prompt fragment has no
legitimate use and confuses the model.
Fixes:
- Add normalizeTreeLayout in pen-core: writes explicit `layout` for
frames missing it (prefers inferLayout, falls back to `vertical`),
strips stale x/y from auto-layout children. Skips the fallback when
any non-overlay child carries explicit x/y — preserves intentional
absolute positioning (phone mockup internals, hero overlays).
- Add unwrapFakePhoneMockups in pen-core: detects fake phone bezels by
name or visual signature (cornerRadius 28-40 + width 240-320) and
either promotes children to the parent (unwrap) or strips the fake
visuals if the fake wrapper is the root itself (sanitize).
- Remove the phone mockup line from jsonl-format.md; gate the in-code
version behind a subtask-label keyword guard.
- Add an explicit NO-PHONE-MOCKUP-WRAPPER instruction for mobile
sub-agents so M2 doesn't self-wrap.
- Fix stale-reference bug in applyPostStreamingTreeHeuristics: after
resolveTreePostPass calls updateNode, the original rootNode reference
is detached; refetch via getNodeById before running normalizeTreeLayout.
- Fix the same bug inside resolveTreePostPass itself: every internal
updateNode call was followed by direct mutations on a `root` parameter
that Zustand had already replaced. Track `currentRoot` and refresh it
after each updateNode.
- Force a canvas resync after the mutation passes via forcePageResync:
in-place mutations on store-owned nodes do not publish; without this
the canvas stays stale on sub-agent retry paths that skip the implicit
updateNode flush. Use forcePageResync (not a hand-rolled shallow doc
spread) because canvas-document-sync subscribes to active page
children identity, not doc identity.
All correctness guarantees are covered by unit tests in pen-core
(normalize-tree-layout.test.ts 13 cases, unwrap-fake-phone-mockup.test.ts
16 cases).
* fix(ai): require cover ratio for icon fallback fuzzy matching
The icon path resolver matched "heart" inside "heartRate-waveform" via
findSubstringFallback and replaced the waveform geometry with the lucide
heart icon, leaving the real waveform invisible. The root cause was that
both prefix and substring fallbacks accepted any matched key of >= 4
characters, regardless of how little of the name it actually covered.
- findPrefixFallback now requires the matched key to cover at least 50%
of the normalized name. "arrowdowncircle" -> "arrowdown" (60%) still
works; "heartratewaveform" -> "heart" (29%) is rejected.
- findSubstringFallback is now suffix-match only (not "anywhere"), with
the same 50% ratio guard. "badgecheck" -> "check" still resolves, but
"starheartbadge" -> "heart" no longer hijacks an unrelated compound
name.
Legitimate chart icons (chart, barchart, analytics, activity, trendingup)
still resolve via exact lookup and are unaffected by the stricter fallback.
* fix(ai): drop redundant section-level fills from sub-agent output
Sub-agents (MiniMax M2 especially) hedge by hardcoding a "safe dark" hex
(#0A0A0A, #111, etc.) on every section root they emit. That fill then
completely covers the page root's intended background color —
#1a1a2e in the health-tracker case — breaking theme switching and
creating visible seams between sections.
Two-layer fix:
1. Prompt guardrail in orchestrator-sub-agent.ts — tell the sub-agent NOT
to set `fill` on its section root, and show the actual inherited
background color so the model has no reason to hedge.
2. Post-pass cleanup stripRedundantSectionFills in pen-core — for each
direct child of the page root frame, drop the fill if:
- the child has no role or a structural role (section/row/column/
stack/container/hero/footer/cta-section/etc.), AND
- the fill matches the root fill exactly OR is one of the common
"safe dark" hexes sub-agents reach for.
Cards, buttons, chips, badges, inputs, phone mockups, status bars,
banners and other protected roles are never touched. Unknown roles
are also preserved (conservative default).
The pass is wired into both applyPostStreamingTreeHeuristics (streaming
path, runs on the outer parent frame via getParentOf so each sub-agent's
section root is visible at the strip scope) and sanitizeNodesForInsert/
Upsert (batch path). All mutations are covered by the existing
forcePageResync call so the canvas re-renders without a stale frame.
* fix(ai): narrow section-fill strip scope to the true page root
Follow-up on
|
||
|
Kayshen Xu
|
3caaa495bb
|
V0.5.2 (#82)
* feat(ai): scaffold pen-ai-skills package
* feat(ai): add pen-ai-skills core types
* feat(ai): add Vite plugin for skill file compilation
* feat(ai): add budget module with token estimation and category-priority trimming
* feat(ai): add skill loader with phase filtering and test injection
* feat(ai): add skill resolver with phase filter, intent match, and dynamic injection
* feat(ai): migrate all prompt content to skill files
Extract prompt content from 7 TypeScript source files into 27 Markdown
skill files with proper frontmatter. Each file contains phase, trigger,
priority, budget, and category metadata for the skill resolution engine.
Planning: decomposition, design-type
Generation: jsonl-format, jsonl-format-simplified, schema, layout,
text-rules, overflow, style-defaults, variables, design-system,
design-code, design-md
Validation: vision-feedback
Maintenance: local-edit, incremental-add, style-consistency
Domains: landing-page, dashboard, mobile-app, form-ui, cjk-typography
Knowledge: role-definitions, design-principles, icon-catalog,
copywriting, examples
* feat(ai): add document context memory module
* feat(ai): add generation history memory module
* feat(ai): wire memory loading into skill resolver
Add memory field to ResolveOptions and load documentContext/generationHistory
into AgentContext with per-phase limits (planning:5, maintenance:3, others:0).
Export memory utility functions from package index.
* refactor(ai): use resolveSkills('planning') in orchestrator
Replace ORCHESTRATOR_PROMPT import with resolveSkills() from pen-ai-skills.
The planning phase system prompt is now resolved dynamically from skill
files instead of a static constant.
* refactor(ai): use resolveSkills('generation') in sub-agent
Replace SUB_AGENT_PROMPT + designPrinciples concatenation with
resolveSkills() from pen-ai-skills. The generation phase system prompt
is now resolved dynamically with flag-based skill filtering for
variables and design.md context.
* refactor(ai): use resolveSkills('validation') in design validation
Replace the 70-line inline VALIDATION_SYSTEM_PROMPT constant with a
lazy resolver function that loads the validation prompt from pen-ai-skills
skill files at call time.
* refactor(mcp): use skill registry for design prompt sections
* refactor(ai): remove old prompt files replaced by pen-ai-skills
Delete prompt files whose content has been migrated to the
pen-ai-skills package:
- ai-prompt-sections.ts (section registry, triggers, builders)
- orchestrator-prompts.ts (orchestrator + sub-agent prompts)
- design-system-prompts.ts (design token generation prompt)
- design-code-prompts.ts (HTML/CSS code-gen prompt)
- design-principles/ directory (5 principle files + index)
Consolidate role-definitions/ 8 sub-files into index.ts
(registerRole calls are runtime behavior, must be preserved).
Move buildDesignMdStylePolicy into ai-prompts.ts. Strip migrated
constants (PEN_NODE_SCHEMA, DESIGN_EXAMPLES, ADAPTIVE_STYLE_POLICY,
CHAT_SYSTEM_PROMPT, DESIGN_GENERATOR_PROMPT, etc.) from ai-prompts.ts.
Add pen-ai-skills alias to mcp:compile esbuild script.
* docs: add pen-ai-skills to architecture documentation
* fix(mcp): use h3 v2 createEventStream API for SSE endpoint
event.node.res was removed in h3 v2. Migrate to createEventStream
which handles SSE headers, streaming, and cleanup automatically.
* chore: update package versions and add pen-ai-skills to Dockerfile
- Bump version for multiple packages to 0.5.2, including pen-ai-skills, pen-codegen, pen-core, pen-figma, pen-renderer, pen-sdk, and pen-types.
- Add pen-ai-skills package to Dockerfile for inclusion in the build process.
- Update TypeScript configuration to ensure proper file inclusion.
- Modify GitHub Actions workflow to trigger on version tags.
- Enhance AI-related functionality by integrating resolveAgentModel for dynamic model resolution in chat and generation APIs.
* refactor: clean up unused imports and improve dynamic content handling
- Removed unused imports from various files, including SkillMeta and ResolvedSkill from types.test.ts, and estimateTokens from resolve-skills.ts.
- Updated the dynamic content injection function to use a more concise parameter in the regex replacement callback.
* chore: enhance build and CI workflows with skill generation
- Added a new script to generate the skill registry during post-installation in package.json.
- Updated the GitHub Actions workflows to include steps for compiling the CLI and generating the skill registry, ensuring all necessary components are built and ready for deployment.
---------
Co-authored-by: Fini <fini.yang@gmail.com>
|
||
|
Kayshen Xu
|
b4d1d2a7bb
|
V0.5.1 (#77)
* fix(docker): support multi-platform builds and fix monorepo paths Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * perf(renderer): cache pre-rasterized paragraph images to avoid per-frame glyph rasterization (#76) * fix(canvas): stabilize frame label size during zoom Draw frame labels in screen-space after the viewport transform restore, converting scene coords manually. Previously fontSize=12/zoom fed into Math.ceil caused integer-boundary jumps that made labels flicker during zoom. Also skip shadow rendering while actively zooming for smoother performance. * perf(renderer): cache pre-rasterized paragraph images to avoid per-frame glyph rasterization - Add paraImageCache (SkImage, 128 MB LRU limit) keyed on the same key as paraCache - Use drawImageRect instead of drawParagraph on cache hit, skipping per-frame glyph shaping and rasterization - Fall back to direct drawParagraph only when off-screen surface creation (MakeSurface) fails - Extract _dpr getter to deduplicate device-pixel-ratio resolution logic across draw paths - Evict oldest entries when cache exceeds byte limit; delete SkImage on eviction and dispose() * feat(cli): introduce OpenPencil CLI for terminal control of the design tool - Added a new CLI application under `apps/cli` to manage OpenPencil from the terminal. - Implemented commands for app control (`start`, `stop`, `status`), document operations (`open`, `save`, `get`, `selection`), and design manipulation (`design`, `import`). - Enhanced documentation with usage instructions and platform support details. - Updated build scripts to include CLI compilation and publishing processes. - Introduced a new GitHub Actions workflow for publishing the CLI to npm. - Updated existing workflows to integrate CLI build steps and ensure proper versioning across packages. * docs: update README files to include CLI tool details and multi-platform code export - Added CLI section to README files in multiple languages, detailing commands for terminal control of the design tool. - Included instructions for global installation and usage examples for the CLI. - Expanded documentation on multi-platform code export capabilities from a single `.op` file to various frameworks. - Updated CLAUDE.md to reference the new CLI documentation and its integration with the design tool. * chore(bun.lock): update package dependencies to specific versions - Removed workspace references for several packages in the bun.lock file. - Updated dependencies for `@zseven-w/pen-core`, `@zseven-w/pen-types`, `@zseven-w/pen-codegen`, `@zseven-w/pen-figma`, and `@zseven-w/pen-renderer` to version `0.5.1-beta.1`. - Ensured consistency in dependency management across the project. --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: leinaldo <60176594+leinaldo@users.noreply.github.com> |
||
|
Kayshen Xu
|
03d4433693
|
V0.5.0 (#67)
* docs: add image search & generation design spec and implementation plan - Spec: dual-source image search (Openverse + Wikimedia), multi-provider image generation - Plan: 16 tasks covering types, server endpoints, settings UI, property panel, auto-search pipeline, MCP integration * feat(types): add image service types and imagePrompt to ImageNode * feat(server): add image service API key validation endpoint Adds POST /api/ai/image-service-test that validates credentials for openverse (client_credentials), openai/custom (Bearer + /v1/models), gemini (API key + v1beta/models), and replicate (Bearer + /v1/models). * feat(server): add multi-provider image generation endpoint * feat(server): add dual-source image search endpoint (Openverse + Wikimedia) POST /api/ai/image-search searches freely-licensed images via Openverse with automatic fallback to Wikimedia Commons on 429 rate-limit responses. Supports optional OAuth credentials for authenticated Openverse requests. * feat(store): add imageSearchStatuses to canvas store for runtime status tracking * feat(store): add image generation config and Openverse OAuth to agent settings * feat(editor): add Images tab to agent settings dialog Adds Popover primitive, ImagesPage component with Image Search (Openverse OAuth, test) and Image Generation (provider select, API key, model, base URL) sections, and wires them into the settings dialog sidebar. * feat(panels): add image search popover with Openverse/Wikimedia results grid * feat(panels): add image generate popover with multi-provider support * feat(panels): add Search and Generate buttons to image property section * feat(ai): update prompts to use imagePrompt instead of src for image nodes * feat(ai): add auto-search pipeline with Openverse/Wikimedia fallback * feat(ai): trigger auto image search after design generation completes * feat(mcp): implement G() operation for image search in batch design DSL Adds the G(parent, mode, prompt) operation to batch_design DSL that creates an image node and optionally fetches a real image URL via the image-search API when mode is "search". Converts executeLine to async to support the network call. * feat(mcp): auto-fill images after design refinement in layered pipeline * feat(ai): split imageSearchQuery and imagePrompt for search vs generation - ImageNode now has both imageSearchQuery (short keywords for search) and imagePrompt (long description for AI image generation) - AI prompts instruct LLM to generate both fields - Search pipeline and popovers use imageSearchQuery - Generate popover uses imagePrompt - Server-side simplifySearchQuery kept as fallback for manual input * fix(ai): hook auto image search into orchestrator completion path The primary generation path uses executeOrchestration -> insertStreamingNode, not applyNodesToCanvas/animateNodesToCanvas. Added scanAndFillImages call to orchestrator.ts after all sub-agents complete. Added debug logging. Removed plan/spec docs from git. * style(editor): remove provider names from image search ready status * fix(panels): clean up image gen error display and settings UI - Parse API error response to show concise message instead of raw JSON - Limit error text to 2 lines with line-clamp - Fix image gen test button sending wrong service name - Inline Image Search ready indicator with section header - Remove debug logging from image search pipeline * style(panels): allow up to 4 lines for image gen error message * fix: avoid 1-frame delay when resizing canvas (#60) rAF callbacks run before ResizeObserver in the same frame. Scheduling render in ResizeObserver via rAF defers it to the next frame. Invoke render() synchronously to leverage ResizeObserver's pre-paint timing and ensure immediate visual update. * feat(electron): implement desktop application structure and auto-updater - Introduced a new Electron desktop application with a structured directory for apps and packages. - Added auto-updater functionality to manage application updates seamlessly. - Created a comprehensive menu system for the desktop app. - Implemented logging capabilities for better debugging and error tracking. - Configured build settings for various platforms (macOS, Windows, Linux) using electron-builder. - Established TypeScript configurations for both the desktop and web applications. - Integrated Vite for the web application with support for React and Tailwind CSS. - Added icons and assets for the desktop application. * chore: update package versions to 0.5.0 across all package.json files and add pre-commit hook for version synchronization - Bumped version to 0.5.0 in package.json files for the main project, desktop app, web app, and all packages. - Introduced a pre-commit hook to automatically sync version numbers from branch names to all package.json files. * chore: update package versions to 0.5.0 and refactor Skia components - Bumped version to 0.5.0 in bun.lock and all relevant package.json files. - Refactored Skia components to utilize shared functionality from @zseven-w/pen-renderer, including image loading, hit testing, and path utilities. - Removed redundant code and improved modularity by re-exporting necessary functions and classes from the renderer package. * fix(panels): handle string fill values in icon nodes (#61) AI-generated icon/path nodes may have fill stored as a raw string instead of a PenFill[] array, causing "Cannot use 'in' operator" crash when selecting the node in the property panel. * chore: update documentation and project structure for monorepo organization - Added a new version bump command to synchronize all package.json files. - Updated the project structure to reflect a monorepo setup with organized workspaces for apps and packages. - Enhanced README files in multiple languages to include the new structure and commands. - Adjusted image paths in documentation to point to the correct locations for the desktop application. * feat(ai): incremental image search and improved image generation prompts - Refactor image search from batch post-generation to incremental queue: enqueueImageForSearch() triggers as each image node is inserted during streaming, so images appear progressively instead of all at once after generation completes. scanAndFillImages() remains as a final sweep. - Update imagePrompt guidance to avoid "transparent background" and similar phrases that many models cannot reliably produce. - Pass node width/height from image panel to generation endpoint for aspect-ratio-aware output (Gemini aspect ratio mapping, OpenAI size selection, Replicate dimensions). * feat(ai): multi-profile image generation config and cleaner error messages - Support multiple image generation profiles with active selection; first configured profile becomes default. Old single-config migrated automatically on hydrate. - Fix Gemini aspect ratio: move to generationConfig.imageConfig per API spec. - Extract clean error messages from provider JSON responses (Gemini error.message, OpenAI error.message, Replicate detail) instead of returning raw JSON text. - Remove destructive client-side regex that mangled error display. * feat(design-md): integrate design system panel and functionality - Added a new DesignMdPanel component for managing design system specifications. - Implemented functionality to toggle the design system panel in the editor layout and toolbar. - Introduced new commands for importing, exporting, and auto-generating design.md content. - Updated AI chat handlers to utilize design.md data for enhanced design generation. - Enhanced localization support for design system features across multiple languages. * perf(canvas): skip draw calls for nodes outside the viewport (#64) Add viewport culling in render() to avoid issuing CanvasKit draw calls for off-screen nodes. A 64px screen-space buffer is kept around the viewport edges so nearby nodes are pre-rendered, preventing pop-in during fast panning. * feat(utils): enhance Windows process spawning for CLI scripts - Updated the buildSpawnClaudeCodeProcess function to handle .cmd and .ps1 scripts appropriately. - Implemented PowerShell invocation for .ps1 files and ensured safe defaults for .cmd and .exe files. - Improved handling of command execution to avoid limitations of cmd.exe. * feat(ai): add support for Gemini CLI integration - Extended the AI provider options to include 'gemini' across various components and APIs. - Implemented functions for generating, validating, and connecting to the Gemini CLI. - Added Gemini-specific error handling and model fetching logic. - Updated UI components to display Gemini as a selectable provider with appropriate icons and labels. - Enhanced localization support for Gemini-related features in multiple languages. * feat(editor): warn before closing with unsaved changes Intercept window/tab close when isDirty is true: - Electron: native dialog with Save / Don't Save / Cancel - Web: beforeunload handler + confirm on New/Open actions - i18n: close-confirm strings for all 15 locales * feat(ipc): extract IPC handlers to a dedicated module - Moved IPC dialog handling and updater functions from main.ts to ipc-handlers.ts for better organization and maintainability. - Implemented file open/save dialogs, theme setting, and preferences management through IPC. - Enhanced updater functionality with state management and auto-update settings. - Improved code structure by separating concerns, making it easier to manage IPC-related logic. * feat(docs): update CLAUDE documentation and add new files for desktop and web apps - Enhanced CLAUDE.md with detailed module documentation references for `packages/` and `apps/`. - Updated `pen-core` description to include clone utilities in `pen-core`. - Added new documentation files for the desktop and web applications, outlining their structure, components, and functionalities. - Included IPC handler details in the desktop app documentation for better clarity on file dialogs and theme synchronization. * feat(docker): add Gemini CLI support and update documentation - Introduced a new Docker build stage for the Gemini CLI, allowing users to install and run it. - Updated the Dockerfile to include the installation of the Gemini CLI alongside existing CLI tools. - Enhanced README files in multiple languages to document the new `openpencil-gemini` image variant. - Added Gemini CLI connection instructions to the main README for better user guidance. * feat(docs): add Gemini CLI connection instructions to multiple language READMEs - Updated README files in German, Spanish, French, Hindi, Indonesian, Japanese, Korean, Portuguese, Russian, Thai, Turkish, Vietnamese, and both Traditional and Simplified Chinese to include connection instructions for the Gemini CLI. - Enhanced documentation to improve user guidance for connecting the Gemini CLI in agent settings. * perf(renderer): replace count-based text cache limits with memory-based eviction (#66) previous limits (PARA_CACHE_MAX=200, TEXT_CACHE_MAX=300) were too small for scenes with many nodes, causing constant cache churn and paragraph rebuilds every frame, which dropped FPS significantly during canvas pan. - switch to byte-budget limits (64 MB paragraphs, 256 MB bitmaps) - bitmap size measured exactly as cw*ch*4; paragraph WASM heap estimated as content.length*64+4096 - eviction uses Map insertion order (FIFO) instead of a separate string[] array, replacing O(n) array.shift() with O(1) Map.entries().next() - evict before insert so the budget check includes the incoming entry --------- Co-authored-by: Fini <fini.yang@gmail.com> Co-authored-by: leinaldo <60176594+leinaldo@users.noreply.github.com> |
Renamed from server/utils/resolve-claude-agent-env.ts (Browse further)