| fix(auth): harden daemon login lifecycle | 3 个月前 |
| feat(ui): colored atom icon on tabs — replaces currentColor with #4A9EFF blue | 5 个月前 |
| feat: multiple enhancements across daemon, webview, and build pipeline - feat(webview-ui): parse attached context files from user messages for attachment pills display instead of raw file content in message bubble - feat(daemon): separate dev build daemon paths from bundled paths; warn with console and VS Code notification when dev build is used - feat(scripts): add targetTriple() mapping platform IDs to Rust cross- compilation targets in bundle-daemon.js - chore: version bump 0.0.6 → 0.0.7 - chore: add build-official scripts to .gitignore - fix(webview): restore relative node_modules path references in bundle - fix(webview): correct CSS source comment paths (src/ → webview-ui/src/) Co-Authored-By: AtomCode (deepseek-v4-flash) <noreply@atomgit.com> | 5 个月前 |
| chore: update remaining 5.0.8 references to 5.0.9 | 2 个月前 |
| chore: update remaining 5.0.8 references to 5.0.9 | 2 个月前 |
| fix(vscode-chat): honor chat font family + make input monospace Reported: chatEditor.fontFamily had no effect on the chat webview, and the input box rendered in the non-monospace UI font. Root cause: VS Code does NOT inject chatEditor.fontFamily into third-party webviews (only a fixed allow-list of CSS vars incl. --vscode-editor-font-family = editor.fontFamily is delivered), and .message-input used font-family: inherit (UI font). - Input box now uses --app-monospace-font-family (unified with code blocks). - New atomcode.chat.fontFamily setting (en + zh-cn). The provider resolves the chat font (atomcode.chat.fontFamily > chatEditor.fontFamily, else fall through to the editor.fontFamily CSS default), sanitizes it for safe CSS inlining, and injects it into the webview HTML via a stable <style id="atomcode-chat-font"> element. - Config changes apply LIVE (a chromeFont postMessage edits that same style rule) without reloading the active chat; the shared style element means a cleared setting truly reverts (an inline removeProperty could not clear a stylesheet rule). Note: the separate path-truncation report is already fixed on main (.tool-name-secondary wraps); it just needs the next extension release. Build outputs (webview/webview.{js,css}) are gitignored; regenerated on build. tsc clean, webview rebuilds, 15/15 webview tests pass. Not machine-verified in a live VS Code host. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Provider-URL: https://gitcode.com/atomgit_atomcode/atomcode | 3 个月前 |
| chore(vscode): remove stray .js build artifacts and update .gitignore | 6 个月前 |
| fix(vscode): harden extension packaging | 6 个月前 |
| fix(vscode): harden extension packaging | 6 个月前 |
| feat: image attachment, dynamic slash skills, and local slash commands - Add image attach/paste support: upload images in chat, send as base64 in request, display image previews in user messages - Add local slash commands (login, logout, whoami, status, config, reload) with display_messages persistence in session - Support dynamic skills from daemon injected into the / slash menu - Add attach menu with file path insert and context file picker - Add append_session_messages API endpoint and client method - Update CSP to allow data: URIs in img-src - Update README slash command list | 4 个月前 |
| chore(release): bump version to v5.0.9 | 2 个月前 |
| chore(vscode): bump version to 0.1.4 | 2 个月前 |
| fix(vscode-chat): honor chat font family + make input monospace Reported: chatEditor.fontFamily had no effect on the chat webview, and the input box rendered in the non-monospace UI font. Root cause: VS Code does NOT inject chatEditor.fontFamily into third-party webviews (only a fixed allow-list of CSS vars incl. --vscode-editor-font-family = editor.fontFamily is delivered), and .message-input used font-family: inherit (UI font). - Input box now uses --app-monospace-font-family (unified with code blocks). - New atomcode.chat.fontFamily setting (en + zh-cn). The provider resolves the chat font (atomcode.chat.fontFamily > chatEditor.fontFamily, else fall through to the editor.fontFamily CSS default), sanitizes it for safe CSS inlining, and injects it into the webview HTML via a stable <style id="atomcode-chat-font"> element. - Config changes apply LIVE (a chromeFont postMessage edits that same style rule) without reloading the active chat; the shared style element means a cleared setting truly reverts (an inline removeProperty could not clear a stylesheet rule). Note: the separate path-truncation report is already fixed on main (.tool-name-secondary wraps); it just needs the next extension release. Build outputs (webview/webview.{js,css}) are gitignored; regenerated on build. tsc clean, webview rebuilds, 15/15 webview tests pass. Not machine-verified in a live VS Code host. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Provider-URL: https://gitcode.com/atomgit_atomcode/atomcode | 3 个月前 |
| fix(vscode-chat): honor chat font family + make input monospace Reported: chatEditor.fontFamily had no effect on the chat webview, and the input box rendered in the non-monospace UI font. Root cause: VS Code does NOT inject chatEditor.fontFamily into third-party webviews (only a fixed allow-list of CSS vars incl. --vscode-editor-font-family = editor.fontFamily is delivered), and .message-input used font-family: inherit (UI font). - Input box now uses --app-monospace-font-family (unified with code blocks). - New atomcode.chat.fontFamily setting (en + zh-cn). The provider resolves the chat font (atomcode.chat.fontFamily > chatEditor.fontFamily, else fall through to the editor.fontFamily CSS default), sanitizes it for safe CSS inlining, and injects it into the webview HTML via a stable <style id="atomcode-chat-font"> element. - Config changes apply LIVE (a chromeFont postMessage edits that same style rule) without reloading the active chat; the shared style element means a cleared setting truly reverts (an inline removeProperty could not clear a stylesheet rule). Note: the separate path-truncation report is already fixed on main (.tool-name-secondary wraps); it just needs the next extension release. Build outputs (webview/webview.{js,css}) are gitignored; regenerated on build. tsc clean, webview rebuilds, 15/15 webview tests pass. Not machine-verified in a live VS Code host. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Provider-URL: https://gitcode.com/atomgit_atomcode/atomcode | 3 个月前 |
| feat(vscode): set up React + esbuild Webview with state management | 6 个月前 |
