Work

Ship it from your phone

A bug report from the beach: text pally the fix and it hands your repo a coding task.

Connect GitHub and pally can queue real coding work on your repos from a text. It briefs the task with your context and messages you when the pull request is ready to review.

Try this recipe

GitHub

iMessage

The routine

How it works

Text pally the repository and the change you want as soon as you spot it. Include the symptom, where it shows up, and the result you expect; a compact bug report is enough. GitHub supplies the repo context, so you do not have to turn the idea into a formal engineering ticket first.

Pally turns your note into a focused coding task and queues it against the GitHub repository you named. The brief carries the practical context from your message, whether that is a timeout on large exports, a small feature request, or a fix tied to a particular part of the product.

The work continues away from your phone while pally keeps track of it. You can ask whether the task is still running or add a clarification if the expected behavior needs tightening. The original request remains the anchor rather than getting lost in a second handoff.

When the coding work produces a pull request, pally texts you the GitHub link and a summary of what changed. You still review the result in the normal place before it becomes part of your codebase; this recipe shortens the path from noticing a problem to having a concrete change ready to inspect.

A useful fit

Good for

Capturing a reproducible bug while away from your desk
Queuing a narrowly described fix in the right repository
Turning a product observation into a coding task
Checking progress from the same text thread
Getting a pull request link when the work is ready

Text it naturally

Things to try

in my api repo, queue a fix for exports timing out on large accounts

send this mobile layout bug to the web repository

add this expected behavior to the github task i just queued

is that coding task still running?

Before you start

Common questions

What should I put in the task text?+

Name the GitHub repository, describe what is wrong or what should change, and include the expected result. A reproduction detail or affected area helps, but you do not need to write a full ticket before pally can brief the work.

Does this merge code into my repository?+

The recipe queues coding work and reports back when a pull request is ready. You get the GitHub link and summary so you can inspect the proposed change through your usual review process.

Can I clarify the request after it starts?+

Yes. Reply with the missing constraint or corrected expected behavior while the task is in context. For a materially different change, describe it separately so the scope of each GitHub task stays clear.

Keep going

Have your own recipe in mind?

Anything you'd hand a great assistant, you can hand pally. Just describe it in a text.

Text Pally