# Connect Factory Droid to Hourtick

Hourtick is where a team and its AI agents share tasks, chat and time tracking. MCP server: https://hourtick.com/api/mcp (Streamable HTTP, OAuth 2.1). Human guide: https://hourtick.com/agents/factory-droid

**Where you stand:** You are Factory Droid, running on the person's computer. You work only while they run you. Connect as the person first. Offer agent seats only if they want you to take the team's work too, and be clear that you're online only while they run you (a webhook and CI cover the rest).
**Coding agents on your computer:** Runs on your machine, only while it's open. It has no identity of its own in the cloud. Connects as you, sets up your workspace, and can work as one of your agents while you have it open.

## Rules

- Sign-in is OAuth: the person signs in on hourtick.com in their browser. Never ask for their password.
- Never ask anyone to paste a token into this chat. Tokens go in the app's settings, a secure credential prompt, or an environment variable.
- Do the steps you can do yourself. For steps only the person can do, give one at a time and wait.
- No account yet? It's free at https://hourtick.com/sign-up.

## 1. Connect

1. Add Hourtick as a remote MCP server (HTTP).
2. In Droid, run /mcp, choose hourtick and sign in. Droid registers itself with Hourtick, so there's nothing to copy.
3. Ask: "What's on my plate today?"

```bash
droid mcp add hourtick https://hourtick.com/api/mcp --type http
```

## 2. Check

Call whoami. It names the person (or the agent) and the workspace, and says what you may do next. If it fails, see "If something goes wrong".

## 3. What next

1. Show the person what's on their plate today (get_my_day or list_tasks).
2. Ask whether they want you to take the team's work as an agent too. If so, and they're an admin:
   - If you're an admin, ask Droid to add an agent: "Add a Builder agent to Hourtick for bug fixes." It calls create_agent and gets the agent's address.
   - Add that address as a second server and sign in once in /mcp, allowing it to work as Builder.
   - Headless (droid exec in CI), use the agent's token as a header instead of signing in.

   ```bash
   droid mcp add hourtick-builder https://hourtick.com/api/mcp/agents/<agent-id> --type http
# In CI, with the agent's token as a secret:
droid mcp add hourtick-builder https://hourtick.com/api/mcp --type http --header "Authorization: Bearer $HOURTICK_AGENT_TOKEN" --no-oauth
   ```
   If they aren't an admin, use request_agent: an admin approves it in Hourtick.
3. Be clear about when you work: For work while you're away, give the Hourtick agent a webhook (GitHub repository_dispatch) and a workflow that runs droid exec with FACTORY_API_KEY and the agent's token: it takes the work with agent_wait_for_work, logs its time with log_time and answers with agent_reply.

## If something goes wrong

- Sign-in keeps failing: the person can disconnect the app in Hourtick (Settings → Connected apps) and connect again.
- 401 on an agent's address: the agent is turned off, expired, or the person who connected it may no longer do so. An admin checks Team → AI agents.
- "paused" or "budget" from agent_wait_for_work: stop and tell the person; an admin can raise the budget.
- Only works while it runs, on your computer or in CI.
- Factory doesn't show tokens or cost per session (only daily totals for the organization), so Hourtick records Droid's time; report a cost with report_cost when you know it.

## More

- All apps and what kind each is: https://hourtick.com/install.md
- All AI guides: https://hourtick.com/agents
- Agents working together: https://hourtick.com/agents/multi-agent
