Everyday tasks in Codelit

For a first task, ask Inspect https://example.com and summarize what you find, replacing the URL with your website. Browser is the website tool. Computer provides a separate hosted desktop for supported work across desktop apps; it does not control your own device. Codelit for Mac is not required.

• Include the page or outcome you care about, such as a pricing page with unclear information.
• Open Browser or Computer from Apps for the live workspace. Back to Thread returns to the conversation.
• Installing an app adds its surface. Hosted access, available capacity, sign-in, and task limits are checked separately. A model API key does not by itself provide a hosted desktop.

Use the connection or resource choice attached to the original task. Sign in to the intended account, select an available destination, and return to that Thread to continue. Do not put passwords, API keys, or login codes into the task prompt.

• A public website may not need a saved website login, but still needs hosted Browser access.
• For a private website, complete its login in Codelit's secure Browser sign-in surface and finish sign-in. Use only the approved website scope.
• If setup could not be checked, use Check again after the service or connection recovers. Nothing can proceed until readiness is confirmed.
• If a start could not be confirmed, check the same task before retrying. A timed-out response does not prove that the server did nothing. Avoid sending a second copy of the request.

The task shows its current status and, when available, its live workspace. Recent activity contains observed progress rather than a guessed completion percentage. Open Evidence for the captured material supporting the result. Hide chat makes more room; Show chat restores your draft.

• Use Stop to request that further work stops. Review the resulting status; stopping does not undo an action already accepted by another service.
• A partial result contains only the findings completed so far. A stopped or failed task is not a successful task.
• Read the reason and preserved findings before retrying. Keep the same Thread so the existing result and task identity remain available.

After an inspection has findings and evidence, ask Send these findings to Slack or Create a GitHub issue from these findings. Choose the exact connected account and channel or repository. For an issue, review the title and full description as well as the repository. For Slack, read the entire outgoing message, including its private Thread link.

You can also ask Prepare a Slack message with these findings or Preview the Slack message for this result. Codelit prepares the same destination and message review, not a search through your Slack history. It still needs your separate approval before sending anything.

• Inspect https://example.com, then send the findings to Slack keeps the delivery tied to that new inspection. It prepares a review; it does not authorize a send.
• Check partial findings carefully before approving delivery. Failed inspections do not produce a successful report.
• Selecting a destination and opening a review do not send anything. An expired or changed review needs a fresh approval.
• A completed delivery needs a provider receipt. If its outcome is unknown, check the destination before retrying; do not assume the message or issue was never created.

Choose Save report to Files on an eligible finished result, or ask Save these findings to Files. If several results could match, choose the exact one. Open in Files returns to the saved report; Reports lists your private saved reports. Saving does not rerun an inspection or send its contents to a connected app.

• A report saves the summary and evidence references, not a permanent copy of every screenshot or live session. Underlying evidence may expire.
• If saving is unconfirmed, Retry save uses the same result. Check Files before assuming that a timed-out save failed.
• Deleting a report leaves its original task intact. Reports belong to the account that saved them.

An eligible completed result offers Make recurring. Review the saved instructions, timing, timezone, limits, and estimated first run before enabling. Saving a routine alone does not enable a schedule. Existing routines can be reopened from Scheduler.

• Direct Browser and Computer routines return results to the Thread. They do not automatically repeat a later Slack delivery.
• Only eligible public read-only Browser routines support unattended checks. A saved private login is not permission for unattended browsing.
• Pause stops future checks, not a check already in progress. Refresh the status before removal; interrupted removal can be retried.
• Use an Agent Team and its reviewed automation controls when you need a reusable multi-step flow or a supported automatic delivery destination.