# AI use cases for Nosis (EvannZhongg/Nosis)

Repo: [EvannZhongg/Nosis](https://github.com/EvannZhongg/Nosis) | Use cases: 3 | Page: https://dedupedai.com/use-cases/evannzhongg-nosis/

Nosis is an open-source, lightweight personal agent application with a terminal UI, a web GUI, and a Bridge process that third-party frontends can drive.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Run a local agent in your terminal with approval controls: https://dedupedai.com/use-cases/evannzhongg-nosis/run-local-agent-in-terminal/
- Manage several agent sessions in a browser GUI: https://dedupedai.com/use-cases/evannzhongg-nosis/manage-agent-sessions-in-gui/
- Build a custom frontend on the Bridge protocol: https://dedupedai.com/use-cases/evannzhongg-nosis/build-custom-frontend-on-bridge/

## How to run a local agent in your terminal with approval controls with Nosis

Repo: [EvannZhongg/Nosis](https://github.com/EvannZhongg/Nosis) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Install Nosis and chat with a personal agent in the terminal, limited to one workspace folder.

**Who it is for:** A developer who wants an AI agent that works on files in a project folder and asks before risky actions.

**The problem:** Chat tools without local file access cannot act on a project, and agents with full access can change files without review.

**The outcome:** A working TUI session in your chosen folder, with the default provider configured and session data saved under ~/.nosis/.

### Steps

1. Install Python 3.11 or newer, Node.js 22 or newer, and uv, then run `git clone https://github.com/EvannZhongg/Nosis.git` and `cd Nosis`.
2. Run `npm install` and then `npm run build` inside the Nosis folder.
3. Run `uv tool install --editable ".[gui]"`.
4. Change into your project folder and run `nosis` once, then quit.
5. Create `~/.nosis/.env` with the line `OPENAI_KEY=your-api-key`, then run `nosis` again.

### Prompt to paste into your agent

```text
Using the Nosis repo at https://github.com/EvannZhongg/Nosis, follow its Quick start to install the TUI, then launch `nosis` from <workspace path>. Report whether ~/.nosis/ was initialized and which permission preset the session starts with. Verify that file tools are limited to <workspace path>.
```

### Caveat

Shell commands run in the workspace sandbox or the host environment depending on scope, so choose the permission preset deliberately before giving the agent broad access.

Risk, credentials: The API key goes into ~/.nosis/.env, so keep that file out of shared folders and version control.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/evannzhongg-nosis/run-local-agent-in-terminal/

## How to manage several agent sessions in a browser GUI with Nosis

Repo: [EvannZhongg/Nosis](https://github.com/EvannZhongg/Nosis) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Run the GUI to keep multiple sessions, attachments, memory, and scheduled tasks in one place.

**Who it is for:** A knowledge worker who juggles several ongoing agent tasks and wants a visual file tree and attachment support.

**The problem:** Terminal sessions are hard to track when several tasks run at once, and files and reminders are scattered across tools.

**The outcome:** A running GUI where you can open multiple sessions, attach files, browse the workspace file tree, and review memory and scheduled tasks.

### Steps

1. Complete the install steps for Nosis, including `uv tool install --editable ".[gui]"`.
2. Run `nosis-gui` in a terminal and leave it running.
3. Open the GUI in your browser at the address the `nosis-gui` process reports, since the README does not list a fixed port. (inferred, check the README)
4. Create a session, attach a file, and send a request that uses it.
5. Open the memory and scheduled task views to review what the agent stored and when it will run next.

### Prompt to paste into your agent

```text
Using the Nosis repo at https://github.com/EvannZhongg/Nosis, start `nosis-gui` and confirm the GUI loads in a browser. Create two sessions for <task name> and report the session list and the workspace file tree. Verify that a session's history is still present after you restart `nosis-gui`.
```

### Caveat

The README leaves the GUI listen address blank, so confirm the address from the process output rather than assuming a default port.

Risk, credentials: Attachments and provider keys are stored on disk under ~/.nosis/, so review what you upload and where the keys live.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/evannzhongg-nosis/manage-agent-sessions-in-gui/

## How to build a custom frontend on the Bridge protocol with Nosis

Repo: [EvannZhongg/Nosis](https://github.com/EvannZhongg/Nosis) | Difficulty: Advanced | Time: 2 hours | Basis: From the README

Drive the Nosis runtime from your own program over newline-delimited JSON on stdio.

**Who it is for:** A developer building a custom interface, script, or integration that needs to control a Nosis agent programmatically.

**The problem:** Existing Nosis frontends do not fit a custom workflow, and the runtime has to be reachable from another process.

**The outcome:** A client program that launches the Bridge, sends requests, and receives agent events through the public protocol.

### Steps

1. Read `docs/bridge-protocol.md` in the Nosis repo to learn the public stdio protocol and message shapes.
2. Read `interfaces/client/README.md` for the lightweight TypeScript client and its process lifecycle example.
3. Launch the installed `nosis-bridge` command as a child process from your program.
4. Send newline-delimited JSON requests on the Bridge stdin and read its events from stdout.
5. Handle frontend interaction requests, such as approvals, so the agent can continue.

### Prompt to paste into your agent

```text
Using the Nosis repo at https://github.com/EvannZhongg/Nosis, read docs/bridge-protocol.md and interfaces/client/README.md, then write a minimal script that launches `nosis-bridge` for <target workspace>. Output the first event the Bridge returns and the list of message types you used. Verify that the script shuts down the Bridge process cleanly.
```

### Caveat

The README says the public protocol and internal Bridge messages are separate, so build only on the documented public protocol and not on internal message types.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/evannzhongg-nosis/build-custom-frontend-on-bridge/