A good place
to begin.

Your first project

Start with a small task in a folder you know.

1. Open Uncensored Coding and choose a working folder.
2. Open Settings and connect a model endpoint.
3. Test the connection and select the model in the top bar.
4. Ask the agent to explain the project structure before making changes.

Read this project's structure and explain how it works.
Do not change files or install anything.

Endpoints & models

Connect the intelligence you want to work with.

In Settings > Endpoints, add an OpenAI-compatible or Anthropic API endpoint. Enter the base URL and an API key if the service requires one.

Use Test to verify the connection. The preview documentation describes automatic context-window detection after a successful test; check the detected value against your server configuration.

Select the model in the top bar. Tool support and output quality depend on that model and its server.

Files, shell & review

Make the task specific and keep its effects visible.

The agent can read files, propose edits and run commands through its configured tools. Tool calls appear in the conversation as expandable groups.

• Confirm the working directory before asking for changes.
• State which files or services must stay untouched.
• Ask for relevant tests and a reviewable diff.
• Read the resulting output before approving the next step.

MCP connectors

Add useful tools without connecting everything.

Open Settings > Connectors. Use a preset or add a connector for the MCP server you want to use.

Connector setup can require a local command, arguments, credentials and installed dependencies. These are specific to the connector. Enable only the tools needed for the task.

The supplied preview includes Google Drive, Memory, MySQL, Postgres, Filesystem and browser-related connectors.

SSH & remote work

Check the target before running a command.

Use Settings > SSH to configure the remote connection. Confirm the host, user and working directory. Do not put production passwords into a conversation.

Start with a read-only inspection. For changes, establish a backup and rollback plan, then verify the result after the action.

Check the current service status and recent errors.
Do not restart services, change files or install packages.
Summarize the findings first.

Computer use

Keep visual actions small and observable.

Desktop tools can provide screenshots, OCR, clicks, scrolling and keyboard input. Availability depends on the installed build and tool configuration.

Use a fresh view of the screen before deciding what to do. Check the result after each meaningful action. Review actions that send data, change permissions or cannot easily be reversed.

Appearance & comfort

Tune the app to your working day.

Settings > Appearance contains theme, accent color, font size, layout density and composer preferences in the supplied preview.

Choose the settings that make code and long conversations comfortable to read, then save your changes.