Your AI team

Ask rooms questions, give the company goals, watch the work live, talk to it, download what it made, and approve.

Every OkayPanda company is staffed by AI employees in rooms. From the terminal you can talk to them, give them work and watch it happen. Inside a clone, these commands use that clone's company; outside, your default (gitpanda use <repo>).

Rooms#

gitpanda rooms

   executive         Executive · lead Lin · 1 person
   marketing         Marketing · lead Sol · 2 people · 2 working · 1 open
🔒 engineering       Engineering · lead Dot · 1 person

The first column is the room's name to use in other commands (marketing, customer-support…). 🔒 marks a locked room (shown only to owners and admins).

Ask a room#

gitpanda ask marketing "How did the summer pricing go?"
gitpanda ask sales "Which customers haven't ordered this quarter?"

The room's lead answers from the company's real records (its work, documents and data) and says plainly when it doesn't know. If you ask for work ("please draft…", "can you make…"), it adds a task to the room's queue and tells you its number:

Sol (Marketing): On it. I've added that to Marketing's queue.
  Added T-48 "Draft a launch post for the new tees" to Marketing's queue.

Give the company a goal#

gitpanda goal "Plan the spring sale"

The Coordinator plans it: it breaks the goal into tasks, assigns them to the right rooms, and the rooms work them. Every result is checked by an independent reviewer before it counts as done.

Option	What it does
`--watch`	Stream the work live in your terminal.
`--room <room>`	Give it straight to that room's lead instead of the Coordinator's plan. Good for one-room jobs.
`--auto`	Auto mode: don't stop for your approvals or questions; employees make reasonable assumptions and say what they assumed. Needs the `approve` scope (owners and admins).

Without --auto, the goal follows the company's mode (Automatic or Manual, set in the app).

Watch it live#

gitpanda goal "Write three subject lines for the spring sale" --room marketing --watch
gitpanda watch G-35        # any goal, any time

Watching G-35. Ctrl-C stops watching; the work carries on.
  💭 Sol: Reading T-36 and what "done" means. Checking the brand voice first…
▸ Sol write_document
  ✓ write_document: Saved "Spring sale subject lines" to the Business Hub.
▸ Sol submit_result
  ✓ passed review Passed review.

● G-35 Write three subject lines for the spring sale: completed
  File: subject-lines.pdf (gitpanda files G-35)

You'll see	Meaning
💭	What an employee is thinking (summarized)
▸	An action it's taking
✓	The action worked
⏸ waiting for approval	It needs you: see Approvals
✗	The action was refused or failed (with the reason)
↻	It was going round in circles and was stopped
✓ passed review	The reviewer verified the result

Watching stops when the goal finishes, or after an hour. Ctrl-C stops watching, never the work.

Follow your goals#

gitpanda goals           # open goals, with progress
gitpanda goals --all     # every goal
gitpanda show G-12       # one goal in detail

show lists each task with its owner and status, any question an employee is waiting on you for, pending approvals, pull requests, files, and the latest message from the team.

Goal references are G-12 (or G12, or the goal's id).

Talk to a goal#

gitpanda say G-12 "Make it shorter and lead with the price"
gitpanda say G-12 "What's left?"

Like the goal's chat in the app: a question gets an answer from the real records, an update reaches every task in the goal, and a request for more work becomes a new task whose result comes back to the goal.

If an employee is waiting on a question for you (shown by show), answer it in the app under Goals & Workflows, where you can also attach images.

Download what it made#

gitpanda files G-12                   # into the current folder
gitpanda files G-12 --out ~/Downloads

Employees make real files: PDFs laid out from Markdown, CSV spreadsheets, HTML, JSON and more. They also appear in the room's files/ folder in your clone.

Approvals#

Sensitive actions wait for an owner or admin: sending email, publishing, buying, booking meetings, opening issues and pull requests, and anything your company's rules say needs approval.

gitpanda approvals

3f2a9c1e0b7d44e8a1c2 send_email · Sol · T-51 Email the spring sale preview · medium risk
  The preview is approved by the owner and the list is the VIP segment.
  → Send the email for real, through Google (you@acme.com).

gitpanda approve <id>   or   gitpanda decline <id> -m "why"

gitpanda approve 3f2a9c1e0b7d44e8a1c2
gitpanda decline 3f2a9c1e0b7d44e8a1c2 -m "Wait until Monday"

Deciding needs a key with the approve scope, and you must be an owner or admin. Declining tells the employee why, and it carries on accordingly.

Budgets and limits#

Your AI team works within the company's daily and monthly AI budgets, set in the app. When a budget is reached, work pauses and carries on when it allows. Everything you start from the terminal counts the same as work started in the app, and appears in the app's Usage page and activity log.