The desktop app
What Code adds inside the SoreQen app, in particular the agent's own browser, research, settings and reporting a problem.
Code in the SoreQen app
Open SoreQen and switch to Code in the title bar. New session gives the agent a fresh, empty folder of its own; it appears in the sidebar once you send its first message. Open a folder… lets it work in one of your projects. Projects in the sidebar fold away with a click on their name.
A new session also shows your usage: sessions, messages, tokens, active days, your busiest hour and favourite model, overall and per model, for all time, 30 days or 7 days.
The browser panel
The agent has a browser of its own, which you can watch live in a panel on the right. Open it with the globe button at the top right, with Ctrl+Shift+B, or with /browser. It also opens by itself the first time the agent opens a page in a session.
- It runs on Firefox. The first time it is needed, SoreQen downloads Firefox for it in the background (about 120 MB, once); until then it uses Chrome or Edge.
- Each session has its own browser, and it is muted.
- You can click, scroll and type in it. + opens a tab, and a new tab lists the dev servers running on your computer. Type an address (
localhost:3000works) or a search. - Closing the panel does not stop the agent's browser; it keeps using it.
Links in a reply open in the browser panel; Ctrl+click (Cmd+click on a Mac) opens them in your own browser. Settings → SoreQen Code swaps the two.
Research
Ask anything that needs the web, such as which library suits a job, what changed in a release, or why an error happens, and SoreQen reads the sources and answers with numbered citations. Ask it to "research X and write a report" for a full report, researched at maximum depth and saved as a file.
Settings
Open Settings from your name at the bottom left, or with Ctrl+,. It holds the theme, text size, transcript width, motion, notifications, your account and plan, usage, models and keys, skills, connectors, memory and updates.
Reporting a problem
In the session where it happened, type:
/feedback what I did, what I saw, what I expectedSoreQen writes a report and opens the folder it is in. The report holds your message, the app's version and the end of its log, with keys and tokens removed. It does not include your code. Send that file, and a screenshot if it is something you can see, to support.
If Code shows "SoreQen Code could not start", press Try again. If it still fails, Copy details copies what went wrong, for your report.
Updates
Fixes to Code arrive by themselves: SoreQen tells you when one is ready, and it applies the next time Code restarts. Updates to the app itself download in the background and install when you choose Restart now, or the next time you quit. Check for updates on the tray icon checks straight away.