> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build an AI app on your Computer

> A working chat app that uses your team agent, runs its procedure, and shows the live tracker.

<Frame caption="Athena 101 · Lesson 18 · Build an AI app on your Computer">
  <iframe src="https://player.vimeo.com/video/1233502130?h=66563aa125&title=0&byline=0&portrait=0&dnt=1" className="w-full aspect-video rounded-xl" frameBorder="0" allow="autoplay; fullscreen; picture-in-picture" allowFullScreen title="Athena 101 · 18 · Build an AI app on your Computer" />
</Frame>

<Accordion title="Transcript">
  Welcome back to Athena 101. Today you'll build an AI app on your Computer. It answers as your team's agent, shows your live tracker, and you can undo any change.

  By the end of this chapter, you'll have a working chat app of your own. It runs on a Computer, a private workspace only you see until you share it. Click the plus button, search for Computer, and pick it. Name it Exceptions Desk. Under Base Template, pick AI Chat. That gives you a chat app that already answers, shows its work, asks for approval and cites its sources. Click Create Computer, and give it a moment to start. Preview shows your new chat app, ready for a job.

  Next, your app answers as Freight Desk, with the instructions, sources and tools your team already set up. Start in Freight Desk's Configuration. Under Toolkits, add AOP, so the app can start the procedures you built. Then click Publish. Your app always uses the published version, never your draft. To connect the app to Freight Desk, open Developer agent on your Computer, and ask for it in your chat. Athena makes the change for you. Now your app answers as Freight Desk, and each person sees only what they're allowed to see.

  Your team can now run the exceptions review right from the app. In Preview, ask it to check this week's carrier files. Freight Desk runs the Exceptions AOP from lesson 15, with the same checks. Nothing gets rebuilt for the app. The card shows it running. When it reaches a step that needs a person, the app asks you first. Read the request, then approve or reject. There's also a choice to approve everything for this session. Leave it off while you're testing. Click Approve. The run finishes and tells you which disputes need attention.

  Your team sees the live Disputes tracker right inside the app. In your chat, ask for it next to the app's chat. It's the live sheet. The disputes from the run you approved are already there. If you have edit access, change a status right here. It updates the same tracker everyone uses. Each person sees it with their own access. Someone who can only view it sees a View Only banner.

  You can undo any change that breaks your app. Before you try one, open Versions and click Snapshot now. Automatic snapshots aren't always on, so take your own before a risky change. Now ask for a layout change. Say it breaks the app. Don't try to fix it by hand. Open Versions, find the snapshot you took, and click Restore. Then confirm. Give it about a minute. Your app comes back the way it was when you took the snapshot. If you picked the wrong one, you can undo it from Versions for 24 hours. This covers your Computer's work. Published Applications keep their own versions, in the next lesson.

  Quick check. You're about to make a risky change to your app. What do you do first? Open Versions and click Snapshot now. If the change breaks the app, restore that snapshot.

  Here's how an audit team uses this. A few people build, and many don't. One builder makes an engagement app on a Computer, and it runs as the firm's methodology agent. It starts the approved sample-testing procedure, and asks before it records a conclusion. The live work paper sits beside the chat. Practitioners never open a procedure editor. They open the app and do the work.

  Try it on your own Computer, with your team's agent and tracker. Look for your agent's reply in Preview, with the live sheet beside it.
</Accordion>

## Before you start

Upload these files from the [Northwind starter kit](/docs/athena-101/starter-kit): **Lesson 18/Disputes tracker.xlsx**, **Northwind dispute SOP.pdf**, **Northwind exception-review checklist.pdf**, and **Workspace setup.txt**.

Use the setup guide to publish Freight Desk and prepare the lesson 15 procedures. Ask your admin for permission to create and use Computers. If your role is denied, watch the builder demonstration. Share the agent, procedures, sources, and tracker separately with testers. Ask for snapshot recovery before trying a breaking change; otherwise, skip recovery practice.

## Steps

<Steps>
  <Step title="Get your own chat app">
    Create a **Computer** named Exceptions Desk. Choose **AI Chat** under **Base Template**, click **Create Computer**, and wait for the app in **Preview**.
  </Step>

  <Step title="Answer as your team agent">
    Make sure Freight Desk can run your saved procedures, then click **Publish**. Ask Athena in the builder chat to make the app answer as Freight Desk.
  </Step>

  <Step title="Run the review in the app">
    In **Preview**, ask for the exceptions review. Read any approval request and choose **Approve** or **Reject**; approve each step separately while testing.
  </Step>

  <Step title="Show the live tracker">
    Ask Athena to place the tracker beside the app’s chat. Check a permitted edit updates the shared sheet and that a viewer sees **View Only**.
  </Step>

  <Step title="Recover a broken change">
    Open **Versions** and click **Snapshot now** before changing the layout. If it breaks, choose that snapshot’s **Restore**, confirm, and check the app returns to its earlier state.
  </Step>
</Steps>

## Try it

> On my Computer, make the app run as my team's agent and show our tracker sheet next to the chat.

Look for your agent’s reply in **Preview**, with the live sheet beside it.

## Next

[Publish it as an Application](/docs/athena-101/19-publish-application)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.